All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] vapic: confine the VAPIC region to 0xc0000..0xe0000
Date: Wed, 26 Aug 2026 20:58:15 +0200	[thread overview]
Message-ID: <b122a57e-7907-48f6-b00a-5eeff6961b27@oss.qualcomm.com> (raw)
In-Reply-To: <20260826181552.848617-3-pbonzini@redhat.com>

On 26/8/26 20:15, Paolo Bonzini wrote:
> The VAPIC region is mapped as writable RAM, at very high priority,
> above existing memory.  If the guest is allowed to map it everywhere,
> it can overlap PCI BARs or even SMRAM.  Ensure that the whole
> region first in the 128K of low memory that are reserved to
> option ROMs.
> 
> Resolves: https://gitlab.com/qemu-project/qemu/-/work_items/4206
> Reported-by: Artem Dinaburg <https://gitlab.com/artem35>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>   hw/i386/vapic.c | 16 +++++++++++++++-
>   1 file changed, 15 insertions(+), 1 deletion(-)

Reviewed-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>


      reply	other threads:[~2026-08-26 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 18:15 [PATCH 0/2] vapic: confine the VAPIC region to 0xc0000..0xe0000 Paolo Bonzini
2026-08-26 18:15 ` [PATCH 1/2] i386/vapic: unref MemoryRegion if vapic_map_rom_writable fails Paolo Bonzini
2026-08-27  9:05   ` Philippe Mathieu-Daudé
2026-08-26 18:15 ` [PATCH 2/2] vapic: confine the VAPIC region to 0xc0000..0xe0000 Paolo Bonzini
2026-08-26 18:58   ` Philippe Mathieu-Daudé [this message]

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=b122a57e-7907-48f6-b00a-5eeff6961b27@oss.qualcomm.com \
    --to=philmd@oss.qualcomm.com \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.