From: Alexey G <x1917x@gmail.com>
To: Yi Sun <yi.y.sun@linux.intel.com>
Cc: Jason Dickens <jdickens@grammatech.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org,
Anthony PERARD <anthony.perard@citrix.com>,
Chao Peng <chao.p.peng@linux.intel.com>
Subject: Re: q35 support in Xen
Date: Tue, 19 Sep 2017 13:35:19 +1000 [thread overview]
Message-ID: <20170919133519.00006a52@gmail.com> (raw)
In-Reply-To: <20170917024911.GA11006@yi.y.sun>
On Sun, 17 Sep 2017 10:49:12 +0800
Yi Sun <yi.y.sun@linux.intel.com> wrote:
> On 17-09-15 23:12:58, Alexey G wrote:
> > On Thu, 14 Sep 2017 16:39:32 +0800
> > Yi Sun <yi.y.sun@linux.intel.com> wrote:
> >
> > > Hi, Alexey,
> > >
> > > Have you submitted the patches? If yes, could you please share the
> > > link?
> >
> > Sorry, had a lot of work recently -- so far I've managed to submit only
> > the bugfix for mentioned xen-mapcache issue with emulated AHCI DMA I/O,
> > which was a main prerequisite for Q35 on Xen.
> >
> > Right now I need to rebase Q35 support patches on recent changes --
> > there were multiple commits to related parts of code in both Xen and
> > QEMU while Q35 patches were initially made for Xen 4.8.0 (which I'm
> > still using at the moment). I'll try rebasing Q35 patches on this
> > weekend, hopefully there will be no big differences with 4.8.
> >
> Thanks a lot for the update! Do you have a plan for the whole feature?
> When do you expect all changes can be submitted or get merged?
Will send the whole set this week, once I refactor patches and write
descriptions for them -- for at least one patch it will be a lenghty one,
I'm afraid. Most Q35 support patches are depend on each other, so it's
easier to send them in a single batch (one for QEMU and one for Xen in
fact).
Rebasing was done only for stable-4.9.0 currently. As patches will be sent
as RFC first, I've decided to delay rebasing to latest staging/master a bit
-- it will require a bit of effort to check the impact of some recent
commits, so it may be a better idea to collect some feedback on RFC patches
targeting stable-4.9.0 and rebase a more or less updated version to staging
then.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-19 3:35 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
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 [this message]
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=20170919133519.00006a52@gmail.com \
--to=x1917x@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=jdickens@grammatech.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yi.y.sun@linux.intel.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 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.