From: "Jan Beulich" <JBeulich@suse.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xensource.com, pmatouse@redhat.com,
qemu-devel@nongnu.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register
Date: Wed, 10 Jun 2015 13:10:22 +0100 [thread overview]
Message-ID: <5578454E02000078000830CD@mail.emea.novell.com> (raw)
In-Reply-To: <20150610134414-mutt-send-email-mst@redhat.com>
>>> On 10.06.15 at 13:46, <mst@redhat.com> wrote:
> I don't really know. The idea would be that device
> is not designed for memory to be disabled when it's
> active, and starts behaving in broken ways.
But you recall that we know the origin of the offending write is in
the hypervisor, and we also know that the device isn't active at the
point the problem occurs?
Jan
next prev parent reply other threads:[~2015-06-10 12:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 14:18 [Qemu-devel] [PATCH][XSA-126] xen: limit guest control of PCI command register Stefano Stabellini
2015-04-01 9:01 ` Michael S. Tsirkin
2015-04-01 9:20 ` Stefano Stabellini
2015-04-01 9:32 ` Michael S. Tsirkin
2015-04-01 9:41 ` [Qemu-devel] [Xen-devel] " Andrew Cooper
2015-04-01 9:59 ` Michael S. Tsirkin
2015-04-13 8:17 ` Jan Beulich
2015-04-13 11:19 ` Michael S. Tsirkin
2015-04-13 11:34 ` Jan Beulich
2015-04-13 11:47 ` Michael S. Tsirkin
2015-04-13 12:40 ` Jan Beulich
2015-04-13 12:47 ` Michael S. Tsirkin
2015-04-13 12:51 ` Jan Beulich
2015-04-20 13:43 ` Michael S. Tsirkin
2015-04-20 14:08 ` Jan Beulich
2015-04-20 14:32 ` Michael S. Tsirkin
2015-04-20 14:57 ` Jan Beulich
2015-06-07 6:23 ` Michael S. Tsirkin
2015-06-08 7:42 ` Jan Beulich
2015-06-08 8:09 ` Malcolm Crossley
2015-06-08 8:59 ` Michael S. Tsirkin
2015-06-08 9:03 ` Jan Beulich
2015-06-08 9:36 ` Michael S. Tsirkin
2015-06-08 10:55 ` Jan Beulich
2015-06-08 11:28 ` Michael S. Tsirkin
2015-06-08 11:44 ` Jan Beulich
2015-06-10 7:00 ` Jan Beulich
2015-06-10 11:43 ` Michael S. Tsirkin
2015-06-10 12:06 ` Jan Beulich
2015-06-10 13:35 ` Michael S. Tsirkin
2015-06-08 9:30 ` Michael S. Tsirkin
2015-06-08 10:38 ` Jan Beulich
2015-06-10 7:08 ` Jan Beulich
2015-06-10 11:46 ` Michael S. Tsirkin
2015-06-10 12:10 ` Jan Beulich [this message]
2015-04-01 9:50 ` Ian Campbell
2015-04-01 10:12 ` Michael S. Tsirkin
2015-04-09 18:10 ` [Qemu-devel] " Peter Maydell
2015-04-10 11:45 ` Peter Maydell
2015-04-10 11:49 ` Peter Maydell
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=5578454E02000078000830CD@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=mst@redhat.com \
--cc=pmatouse@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).