All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@citrix.com>,
	Lars Kurth <lars.kurth@citrix.com>
Cc: xen-devel@lists.xenproject.org, committers@xenproject.org
Subject: Re: [PATCH] Move missing items from docs/misc/qemu-xen-security to SUPPORT.md
Date: Fri, 09 Mar 2018 03:49:26 -0700	[thread overview]
Message-ID: <5AA274C602000078001B02A1@prv-mh.provo.novell.com> (raw)
In-Reply-To: <c13abc63-56cc-5335-627a-ed66521a5eb7@citrix.com>

>>> On 09.03.18 at 11:30, <george.dunlap@citrix.com> wrote:
> On 03/09/2018 10:07 AM, Jan Beulich wrote:
>>>>> On 08.03.18 at 18:37, <lars.kurth@citrix.com> wrote:
>>> --- a/SUPPORT.md
>>> +++ b/SUPPORT.md
>>> @@ -620,6 +620,7 @@ Note that other devices are available but not security supported.
>>>  
>>>  ### x86/Emulated platform devices (QEMU):
>>>  
>>> +    Status, PCI host bridge: Supported
>>>      Status, piix3: Supported
>> 
>> That's way too generic imo: Any chipset will have a host bridge, so
>> its support is already included in the statement on which chipset
>> emulation(s) we support. By adding what you add, you could again
>> raise the expectation that any host bridge implementation in qemu
>> is supported.
> 
> Yes, when I saw Lars' patch I was trying to remember why those things
> weren't already copied over, and was pretty sure there was a good reason.
> 
> Are you saying, in effect, that "support for piix3" *implies* support
> for the PCI host bridge provided by the piix3 chipset?

Yes.

> If so, "PCI host bridge" was redundant, and may have been put in before
> piix3 was specified.

Likely.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-03-09 10:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 17:37 [PATCH] Move missing items from docs/misc/qemu-xen-security to SUPPORT.md Lars Kurth
2018-03-08 17:44 ` Ian Jackson
2018-03-08 18:07   ` Lars Kurth
2018-03-09 10:08     ` Jan Beulich
2018-03-09 10:29       ` Lars Kurth
2018-03-09 10:32     ` George Dunlap
2018-03-09 10:34       ` Lars Kurth
2018-03-09 10:38         ` George Dunlap
2018-03-09 10:41           ` Lars Kurth
2018-03-09 10:07 ` Jan Beulich
2018-03-09 10:28   ` Lars Kurth
2018-03-09 10:53     ` Jan Beulich
2018-03-09 10:30   ` George Dunlap
2018-03-09 10:49     ` Jan Beulich [this message]
2018-03-09 10:31 ` Julien Grall
2018-03-09 10:35   ` Lars Kurth
2018-03-09 10:36   ` George Dunlap

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=5AA274C602000078001B02A1@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=committers@xenproject.org \
    --cc=george.dunlap@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xenproject.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.