From: 'Joerg Roedel' <joro@8bytes.org>
To: Avi Kivity <avi@redhat.com>
Cc: "Han, Weidong" <weidong.han@intel.com>,
'Mark McLoughlin' <markmc@redhat.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"Woodhouse, David" <david.woodhouse@intel.com>,
"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
'Jesse Barnes' <jbarnes@virtuousgeek.org>,
"'iommu@lists.linux-foundation.org'"
<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH 08/13] allocation and free functions of virtual machine domain
Date: Fri, 5 Dec 2008 20:22:24 +0100 [thread overview]
Message-ID: <20081205192224.GC26459@8bytes.org> (raw)
In-Reply-To: <49395B49.5060302@redhat.com>
On Fri, Dec 05, 2008 at 06:48:09PM +0200, Avi Kivity wrote:
> Han, Weidong wrote:
> >
> >Will Avi merge intel-iommu changes into his master tree? If yes, we can
> >push my patches and Joerg's patches together. Otherwise, I need rebase my
> >patches to dwmw2's tree and push it into there first.
> >
>
> I think the iommu patches should be merged into Dave's tree first; I'll
> pull from that and apply the kvm patches.
>
> It all needs to be done soonish as 2.6.28 is imminent.
Ok, I will send the AMD IOMMU specific parts upstream via Ingo's tree in
a way that does not conflict with Han's patches and the IOMMU-API code
when Linus pulls it.
And as soon as Han sends out his rebased patchset I will rebase the
IOMMU-API too and then everything should be fine.
Joerg
next prev parent reply other threads:[~2008-12-05 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 14:22 [PATCH 08/13] allocation and free functions of virtual machine domain Han, Weidong
2008-12-04 17:13 ` Mark McLoughlin
2008-12-04 23:17 ` Joerg Roedel
2008-12-05 9:20 ` Mark McLoughlin
2008-12-05 9:33 ` Han, Weidong
2008-12-05 16:48 ` Avi Kivity
2008-12-05 19:22 ` 'Joerg Roedel' [this message]
2008-12-06 2:14 ` Han, Weidong
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=20081205192224.GC26459@8bytes.org \
--to=joro@8bytes.org \
--cc=avi@redhat.com \
--cc=david.woodhouse@intel.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=weidong.han@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.