From: "Andreas Färber" <afaerber@suse.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses
Date: Mon, 05 Aug 2013 11:34:53 +0200 [thread overview]
Message-ID: <51FF71BD.5040400@suse.de> (raw)
In-Reply-To: <51FCBFCD.5020608@web.de>
Am 03.08.2013 10:31, schrieb Jan Kiszka:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> 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>
> ---
> exec.c | 3 ++-
> include/exec/ioport.h | 2 ++
> ioport.c | 16 ++++++++++++++++
> 3 files changed, 20 insertions(+), 1 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 3ca9381..9ed598f 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -1820,7 +1820,8 @@ static void memory_map_init(void)
> address_space_init(&address_space_memory, system_memory, "memory");
>
> system_io = g_malloc(sizeof(*system_io));
> - memory_region_init(system_io, NULL, "io", 65536);
> + memory_region_init_io(system_io, NULL, &unassigned_io_ops, NULL, "io",
> + 65536);
It was reported that there may be some machines/PHBs that have
overlapping PIO/MMIO. Unless we use priorities, this ..._io MemoryRegion
will shadow or conflict with any ..._io MemoryRegion added to the memory
address space, wouldn't it?
Regards,
Andreas
> address_space_init(&address_space_io, system_io, "I/O");
>
> memory_listener_register(&core_memory_listener, &address_space_memory);
> diff --git a/include/exec/ioport.h b/include/exec/ioport.h
> index bdd4e96..84f7f85 100644
> --- a/include/exec/ioport.h
> +++ b/include/exec/ioport.h
> @@ -45,6 +45,8 @@ typedef struct MemoryRegionPortio {
>
> #define PORTIO_END_OF_LIST() { }
>
> +extern const MemoryRegionOps unassigned_io_ops;
> +
> void cpu_outb(pio_addr_t addr, uint8_t val);
> void cpu_outw(pio_addr_t addr, uint16_t val);
> void cpu_outl(pio_addr_t addr, uint32_t val);
> diff --git a/ioport.c b/ioport.c
> index 79b7f1a..9765588 100644
> --- a/ioport.c
> +++ b/ioport.c
> @@ -44,6 +44,22 @@ typedef struct MemoryRegionPortioList {
> MemoryRegionPortio ports[];
> } MemoryRegionPortioList;
>
> +static uint64_t unassigned_io_read(void *opaque, hwaddr addr, unsigned size)
> +{
> + return -1UL;
> +}
> +
> +static void unassigned_io_write(void *opaque, hwaddr addr, uint64_t val,
> + unsigned size)
> +{
> +}
> +
> +const MemoryRegionOps unassigned_io_ops = {
> + .read = unassigned_io_read,
> + .write = unassigned_io_write,
> + .endianness = DEVICE_NATIVE_ENDIAN,
> +};
> +
> void cpu_outb(pio_addr_t addr, uint8_t val)
> {
> LOG_IOPORT("outb: %04"FMT_pioaddr" %02"PRIx8"\n", addr, val);
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-05 9:35 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 [this message]
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
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=51FF71BD.5040400@suse.de \
--to=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=jan.kiszka@web.de \
--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).