From d7ec83e6b57f48cf07f663e232e4aa2b32bc33c7 Mon Sep 17 00:00:00 2001 From: Avi Kivity Date: Wed, 8 Feb 2012 17:07:26 +0200 Subject: memory: don't pass ->readable attribute to cpu_register_physical_memory_log It can be derived from the MemoryRegion itself (which is why it is not used there). Signed-off-by: Avi Kivity Reviewed-by: Richard Henderson --- exec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'exec.c') diff --git a/exec.c b/exec.c index b81677ade..d3020ab57 100644 --- a/exec.c +++ b/exec.c @@ -2529,7 +2529,7 @@ static subpage_t *subpage_init (target_phys_addr_t base, ram_addr_t *phys, before calculating this offset. This should not be a problem unless the low bits of start_addr and region_offset differ. */ void cpu_register_physical_memory_log(MemoryRegionSection *section, - bool readable, bool readonly) + bool readonly) { target_phys_addr_t start_addr = section->offset_within_address_space; ram_addr_t size = section->size; -- cgit v1.2.3