qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 for 1.6 1/2] memory: Provide separate handlin


From: Jan Kiszka
Subject: Re: [Qemu-devel] [PATCH v2 for 1.6 1/2] memory: Provide separate handling of unassigned io ports accesses
Date: Mon, 02 Sep 2013 18:02:52 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2013-09-02 17:58, Andreas Färber wrote:
> Am 02.09.2013 17:56, schrieb Jan Kiszka:
>> On 2013-09-02 15:52, Peter Maydell wrote:
>>> On 12 August 2013 16:39, Andreas Färber <address@hidden> wrote:
>>>> Am 12.08.2013 17:29, schrieb Jan Kiszka:
>>>>> Accesses to unassigned io ports shall return -1 on read and be ignored
>>>>> on write. Ensure these properties via dedicated ops, decoupling us from
>>>>> the memory core's handling of unassigned accesses.
>>>>>
>>>>> Signed-off-by: Jan Kiszka <address@hidden>
>>>>> ---
>>>>>
>>>>> Changes in v2:
>>>>>  - avoid breakage in ioport.h for user build
>>>>
>>>> Looks OK, but if you want Anthony to apply this for rc3 then please
>>>> repost as a full, top-level series.
>>>
>>> It looks like this never happened, so this bug is still present
>>> in master :-(  [noticed by stsquad since integratorcp is busted too].
>>
>> I suppose the repost just fell through the cracks at the end of the
>> release cycle. Let me re-repost the whole thing, CC'ing stable.
> 
> I vaguely remember you reposting 2/2 top-level only and asking Anthony
> to fix his tool instead, which was quite apparently not helpful. ;)

Well, I wasn't expecting this to happen within the release cycle. But I
would still appreciate having to do such thread-breaking updates in the
future.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux



reply via email to

[Prev in Thread] Current Thread [Next in Thread]