qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
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	[thread overview]
Message-ID: <5224B6AC.1010702@siemens.com> (raw)
In-Reply-To: <5224B5B8.1090206@suse.de>

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 <afaerber@suse.de> 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 <jan.kiszka@siemens.com>
>>>>> ---
>>>>>
>>>>> 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	other threads:[~2013-09-02 16:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 12:01 [Qemu-devel] [PATCH for 1.6 0/2] Fix unassigned memory and I/O access handling Jan Kiszka
2013-08-09 12:01 ` [Qemu-devel] [PATCH for 1.6 1/2] memory: Provide separate handling of unassigned io ports accesses Jan Kiszka
2013-08-12 14:34   ` Anthony Liguori
2013-08-12 15:29     ` [Qemu-devel] [PATCH v2 " Jan Kiszka
2013-08-12 15:39       ` Andreas Färber
2013-09-02 13:52         ` Peter Maydell
2013-09-02 15:56           ` Jan Kiszka
2013-09-02 15:58             ` Andreas Färber
2013-09-02 16:02               ` Jan Kiszka [this message]
2013-08-12 15:41       ` Anthony Liguori
2013-08-09 12:01 ` [Qemu-devel] [PATCH for 1.6 2/2] Revert "memory: Return -1 again on reads from unsigned regions" Jan Kiszka
2013-08-09 17:33   ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2013-08-12 16:46 [Qemu-devel] [PATCH v2 for 1.6 1/2] memory: Provide separate handling of unassigned io ports accesses Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5224B6AC.1010702@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).