All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"committers@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:53:27 -0700	[thread overview]
Message-ID: <5AA275B702000078001B02B5@prv-mh.provo.novell.com> (raw)
In-Reply-To: <17BAC847-D2D7-4D35-9318-38478066834E@citrix.com>

>>> On 09.03.18 at 11:28, <lars.kurth@citrix.com> wrote:
> On 09/03/2018, 11:07, "Jan Beulich" <JBeulich@suse.com> 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.
> 
> I thought this may be an issue. I would be quite happy to change it, but 
> would need to know how to phrase it.
> Suggestions?

Just drop this addition of a line.

>     >  ### x86/Emulated graphics (QEMU):
>     >  
>     >      Status, cirrus-vga: Supported
>     > -    Status, stgvga: Supported
>     > +    Status, stdvga: Supported
>     > +    Status, xenfb: Supported
>     
>     Just like xen_disk (correctly) isn't listed in the "x86/Emulated storage
>     (QEMU)" section, xenfb doesn't belong here imo. It's not an emulated
>     device, and is already enumerated in "PV Framebuffer (backend)"
>     (just not with the term "xenfb").
> 
> So, what I read from this, the existing line 
> 
> ### PV Framebuffer (backend)
>     Status, QEMU: Supported
> 
> covers the back-end.

Yes.

>     > @@ -650,7 +659,9 @@ Note that other devices are available but not security supported.
>     >      Status, usbtablet: Supported
>     >      Status, ps/2 keyboard: Supported
>     >      Status, ps/2 mouse: Supported
>     > -
>     > +    Status, xenfb keyboard: Supported
>     > +    Status, xenfb mouse: Supported
>     
>     Similarly for these ones and "PV keyboard (backend)". Perhaps a
>     "PV mouse (backend)" section should be added.
>  
> So to clarify, 
> 
> ### PV keyboard (backend)
>     Status, QEMU: Supported
> ### PV mouse (backend)
>     Status, QEMU: Supported
> 
> would cover this in your view?

Yes.

> Does this cover all the bases, or did I miss anything? 

With s/bases/backends/ - yes, I think so.

> In other words, are there any frontend bits for xenfb (framebuffer, 
> keyboard, mouse) that would need to be recorded somewhere

The frontend are in the guest OSes anyway, and they all have their
own sections (looks like as for the backends there's "keyboard" but
not "mouse"; in both cases not unlikely because they live close
together).

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:53 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 [this message]
2018-03-09 10:30   ` George Dunlap
2018-03-09 10:49     ` Jan Beulich
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=5AA275B702000078001B02B5@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=committers@xenproject.org \
    --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.