From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/8] Patchset to enable vt-d support for kvm/ia64.
Date: Thu, 02 Oct 2008 13:06:12 +0000 [thread overview]
Message-ID: <48E4C744.9060403@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01A53DEF@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> In order to enable vt-d suport for kvm/ia64 guests, I worked out the
> patchset to make it happen. Please review. The first five patches have
> no changes for logic and just do code move.
> Xiantao
> [PATCH 1/8] kvm/vt-d: Moving vtd.c from arch/x86/kvm/ to virt/kvm/
> [PATCH 2/8] kvm: Moving device_assignment logic to kvm_main.c
> [PATCH 3/8] kvm: Changing is_mmio_pfn to kvm_is_mmio_pfn, and make it
> common
> [PATCH 4/8] kvm: Split arch/x86/kvm/irq.c to two parts.
> [PATCH 5/8] kvm: Moving irqchip_in_kernel from ioapic.h to irq.h
> [PATCH 6/8] kvm/ia64: Make pmt table be able to hold physical mmio
> entries.
> [PATCH 7/8] kvm/ia64: Add directed mmio range support for kvm guests.
> [PATCH 8/8] kvm/ia64: Add intel iommu support for guests
>
Apart from my comment on patch 4, this series looks good.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 0/8] Patchset to enable vt-d support for kvm/ia64.
Date: Thu, 02 Oct 2008 16:06:12 +0300 [thread overview]
Message-ID: <48E4C744.9060403@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01A53DEF@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> In order to enable vt-d suport for kvm/ia64 guests, I worked out the
> patchset to make it happen. Please review. The first five patches have
> no changes for logic and just do code move.
> Xiantao
> [PATCH 1/8] kvm/vt-d: Moving vtd.c from arch/x86/kvm/ to virt/kvm/
> [PATCH 2/8] kvm: Moving device_assignment logic to kvm_main.c
> [PATCH 3/8] kvm: Changing is_mmio_pfn to kvm_is_mmio_pfn, and make it
> common
> [PATCH 4/8] kvm: Split arch/x86/kvm/irq.c to two parts.
> [PATCH 5/8] kvm: Moving irqchip_in_kernel from ioapic.h to irq.h
> [PATCH 6/8] kvm/ia64: Make pmt table be able to hold physical mmio
> entries.
> [PATCH 7/8] kvm/ia64: Add directed mmio range support for kvm guests.
> [PATCH 8/8] kvm/ia64: Add intel iommu support for guests
>
Apart from my comment on patch 4, this series looks good.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-02 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 5:25 [PATCH 0/8] Patchset to enable vt-d support for kvm/ia64 Zhang, Xiantao
2008-09-29 5:25 ` Zhang, Xiantao
2008-10-02 13:06 ` Avi Kivity [this message]
2008-10-02 13:06 ` Avi Kivity
2008-10-02 15:14 ` Zhang, Xiantao
2008-10-02 15:14 ` Zhang, Xiantao
2008-10-02 15:32 ` Avi Kivity
2008-10-02 15:32 ` Avi Kivity
2008-10-03 2:13 ` Zhang, Xiantao
2008-10-03 2:13 ` Zhang, Xiantao
2008-10-07 9:47 ` Avi Kivity
2008-10-07 9:47 ` Avi Kivity
2008-10-07 9:50 ` Zhang, Xiantao
2008-10-07 9:50 ` Zhang, Xiantao
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=48E4C744.9060403@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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.