From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Jan Kiszka" <jan.kiszka@web.de>,
"Andreas Färber" <afaerber@suse.de>,
"Aurelien Jarno" <aurelien@aurel32.net>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses
Date: Mon, 5 Aug 2013 13:10:04 +0200 [thread overview]
Message-ID: <20130805111004.GD19162@mail.corp.redhat.com> (raw)
In-Reply-To: <CAFEAcA9RhdYiGk7OJ8_Kf329ynzMCeDeQEuSB6tV6dNUbrTwCw@mail.gmail.com>
On Aug 05 2013, Peter Maydell wrote:
> > But even if we would, the IO container now catches all accesses, so
> > the system memory region will never have its default handler run for
> > that window.
>
> Yes, that is the point -- before the IO container caught all
> accesses, the default handler that would run would be the
> system memory region, but now that the IO container has
> default read/write ops they will take precedence. So this
> would be a behaviour change if there are any boards set up
> like this. (I'm not sure there are any, though.)
Before 1.6 this would have happened anyway. Before 1.6, all
I/O accesses would go through cpu_in/cpu_out, and would never
hit the system memory region. So Jan's patch is effectively
restoring old behavior.
Paolo
next prev parent reply other threads:[~2013-08-05 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 8:31 [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses Jan Kiszka
2013-08-05 9:34 ` Andreas Färber
2013-08-05 9:38 ` Jan Kiszka
2013-08-05 9:59 ` Peter Maydell
2013-08-05 10:29 ` Andreas Färber
2013-08-05 10:30 ` Jan Kiszka
2013-08-05 10:36 ` Peter Maydell
2013-08-05 10:44 ` Jan Kiszka
2013-08-05 10:51 ` Peter Maydell
2013-08-05 11:03 ` Jan Kiszka
2013-08-05 11:35 ` Andreas Färber
2013-08-05 11:38 ` Jan Kiszka
2013-08-05 11:10 ` Paolo Bonzini [this message]
2013-08-05 11:07 ` Paolo Bonzini
2013-08-05 20:19 ` Richard Henderson
2013-08-08 15:33 ` Peter Maydell
2013-08-08 15:43 ` Jan Kiszka
2013-08-09 7:41 ` Paolo Bonzini
2013-08-09 16:49 ` Andreas Färber
2013-08-09 18:48 ` Richard Henderson
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=20130805111004.GD19162@mail.corp.redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=jan.kiszka@web.de \
--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).