All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Peng <chao.p.peng@linux.intel.com>
To: Alexey G <x1917x@gmail.com>, Jason Dickens <jdickens@grammatech.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: q35 support in Xen
Date: Thu, 29 Jun 2017 21:28:14 +0800	[thread overview]
Message-ID: <1498742894.3583.10.camel@linux.intel.com> (raw)
In-Reply-To: <20170629060327.000015c8@gmail.com>


> Anthony Perard did a great job providing patches which add a partial
> Q35
> support. I tried extending his patches to include missing features for
> Q35 in
> hvmloader, libacpi and QEMU and so far the Xen+Q35 experience is quite
> positive

Hi Alexey, 

I saw Anthony's patch, but your extension patch seems still in
development. Do you have plan to upstream it? I'm also interested in
this basically I want full PCI-e passthru capability (Current Xen does
support passthru a PCI-e device but guest can't see configuration offset
256-4095 for example). I'm glad to collaborate on this.

Thanks,
Chao


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

  reply	other threads:[~2017-06-29 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 17:55 q35 support in Xen Jason Dickens
2017-06-27  9:19 ` Wei Liu
2017-06-27 16:36   ` Anthony PERARD
2017-06-27 18:48     ` Jason Dickens
2017-06-28 20:03       ` Alexey G
2017-06-29 13:28         ` Chao Peng [this message]
2017-06-29 20:03           ` Alexey G
2017-06-29 20:18             ` Stefano Stabellini
2017-06-30 10:21             ` Wei Liu
2017-09-14  8:39             ` Yi Sun
2017-09-15 13:12               ` Alexey G
2017-09-17  2:49                 ` Yi Sun
2017-09-19  3:35                   ` Alexey G
2017-09-19  5:31                     ` Yi Sun

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=1498742894.3583.10.camel@linux.intel.com \
    --to=chao.p.peng@linux.intel.com \
    --cc=anthony.perard@citrix.com \
    --cc=jdickens@grammatech.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=x1917x@gmail.com \
    --cc=xen-devel@lists.xen.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.