From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>
Cc: markmb@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fw_cfg DMA security
Date: Fri, 23 Oct 2015 09:29:54 +0200 [thread overview]
Message-ID: <5629E1F2.5020005@redhat.com> (raw)
In-Reply-To: <1445583386.13733.134.camel@redhat.com>
On 23/10/2015 08:56, Gerd Hoffmann wrote:
>> >
>> > So, for example, since Red Hat is working on SMM. Would a DMA to SMRAM
>> > be protected?
>> >
>> > I haven't watched the fw_cfg DMA discussion too closely, but has this
>> > been thought about?
> Yes. That problem isn't new and it isn't specific to fw_cfg. You also
> don't want grant dma access to smram/tseg to your ide/sata/scsi
> controller or NIC.
>
> > One idea I had was that near the end of the firmware boot, the
> > firmware could trigger fw_cfg in QEMU to stop supporting DMA until a
> > reset.
>
> Should not be needed. We have address spaces in qemu, and the
> smram/tseg regions are explicitly excluded (when enabled) from dma-able
> memory.
Exactly. SMRAM/TSEG is only added to CPU address spaces: for TCG, it's
enabled specifically when the processor enters SMM and disabled upon
RSM; for KVM, it's added to hypervisor address space 1, which is only
looked up for processors that are in SMM.
Paolo
next prev parent reply other threads:[~2015-10-23 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 6:27 [Qemu-devel] fw_cfg DMA security Jordan Justen
2015-10-23 6:56 ` Gerd Hoffmann
2015-10-23 7:29 ` Paolo Bonzini [this message]
2015-10-23 9:49 ` Marc Marí
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=5629E1F2.5020005@redhat.com \
--to=pbonzini@redhat.com \
--cc=jordan.l.justen@intel.com \
--cc=kraxel@redhat.com \
--cc=markmb@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.