[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2] exec.c: Fix subpage memory access to RAM Mem
From: |
Avi Kivity |
Subject: |
Re: [Qemu-devel] [PATCH v2] exec.c: Fix subpage memory access to RAM MemoryRegion |
Date: |
Thu, 01 Dec 2011 19:24:14 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0 |
On 12/01/2011 07:18 PM, Andreas Färber wrote:
> Am 01.12.2011 11:06, schrieb Gleb Natapov:
> > On Thu, Dec 01, 2011 at 11:54:33AM +0200, Avi Kivity wrote:
> >> On 12/01/2011 11:47 AM, Gleb Natapov wrote:
> >>> On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
> >>>> On 12/01/2011 11:37 AM, Gleb Natapov wrote:
> >>>>>>
> >>>>>> Looks reasonable. Should go into 1.1. Should we backport it to
> >>>>>> 1.0.blah? From 95c318f's description, it doesn't happen in normal
> >>>>>> circumstances.
> >>>>>>
> >>>>> To reproduce that I mappped subpage PCI bar over RAM IIRC.
> >>>>
> >>>> In qemu 1.0, you can no longer do that (the pci bridge will not let the
> >>>> BAR override the RAM).
> >>>>
> >>>
> >>> Hmm, if this is how real HW work then problem solved :) (different HW can
> >>> behave differently, but it is reasonable to assume that on a PC memory
> >>> access below TOM will be redirected to memory controller no matter what)
>
> Ah, glad to know that x86_64 is no longer affected. What about 0.15.1?
In 0.15 this can still happen, 1.0 was fixed by the memory API. Note
the fix is actually a side effect of a different change, and the issue
can still happen for other reasons (as in your case).
--
error compiling committee.c: too many arguments to function
Re: [Qemu-devel] [PATCH v2] exec.c: Fix subpage memory access to RAM MemoryRegion, Andreas Färber, 2011/12/09