xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth@citrix.com>, xen-devel@lists.xenproject.org
Cc: committers@xenproject.org
Subject: Re: [PATCH] Move missing items from docs/misc/qemu-xen-security to SUPPORT.md
Date: Fri, 9 Mar 2018 10:31:16 +0000	[thread overview]
Message-ID: <8f5736eb-a423-dbd4-48d6-1eead967e4fa@arm.com> (raw)
In-Reply-To: <20180308173719.14791-1-lars.kurth@citrix.com>

Hi Lars,

On 08/03/18 17:37, Lars Kurth wrote:
> x86/Emulated platform devices (QEMU):
> - Aded PCI host bridge (as in xen.git:docs/misc/qemu-xen-security)
> New: x86/Emulated Storage Image Formats
> - Added raw, qcow, qcow2, vhd (as in xen.git:docs/misc/qemu-xen-security)

Is there any reason to be x86/emulate storage only? If I am not 
mistaken, QEMU could also be used as PV block backend for all those 
image formats. That is also working on Arm.

Cheers,

-- 
Julien Grall

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

  parent reply	other threads:[~2018-03-09 10:31 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
2018-03-09 10:31 ` Julien Grall [this message]
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=8f5736eb-a423-dbd4-48d6-1eead967e4fa@arm.com \
    --to=julien.grall@arm.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 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).