kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH 2/8]kvm: Moving device_assignment logic to kvm_main.c
Date: Fri, 3 Oct 2008 13:12:51 +0530	[thread overview]
Message-ID: <200810031312.52056.amit.shah@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01A541E8@pdsmsx415.ccr.corp.intel.com>

* On Friday 03 Oct 2008 13:02:05 Zhang, Xiantao wrote:
> Amit Shah wrote:
> > * On Monday 29 Sep 2008 10:56:29 Zhang, Xiantao wrote:
> >> From: Xiantao Zhang <xiantao.zhang@intel.com>
> >> Date: Sat, 27 Sep 2008 10:59:36 +0800
> >> Subject: [PATCH] kvm: Moving device_assignment logic to kvm_main.c
> >>
> >> To share with other archs, this patch moves device_assignment
> >> logic to common parts.
> >> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> >>
> >> diff --git a/include/linux/kvm.h b/include/linux/kvm.h
> >> index 4269be1..9acf34a 100644
> >> --- a/include/linux/kvm.h
> >> +++ b/include/linux/kvm.h
> >> @@ -383,7 +383,9 @@ struct kvm_trace_rec {
> >>  #define KVM_CAP_MP_STATE 14
> >>  #define KVM_CAP_COALESCED_MMIO 15
> >>  #define KVM_CAP_SYNC_MMU 16  /* Changes to host mmap are reflected
> >> in guest */ +#ifdef CONFIG_X86
> >>  #define KVM_CAP_DEVICE_ASSIGNMENT 17
> >> +#endif
> >
> > I didn't see this changed to also accomodate IA64 in the patchset.
>
> Since linux-ia64 DMAR is not ready in kvm.git, and it should be in
> linux-ia64.git. So it should be in kvm.git once Avi merged with

OK; Does Linus' tree currently have the necessary support?

Also, I think you'll have to redo the patch 1/8 after Weidong's mmio patch got 
merged.

> upstream, so I didn't enable it for kvm/ia64 now.  You know, S390 has no
> pci support, so if we put the code in kvm_mainc, we should use the macro
> to exclude other arch which doesn't need device assignments.  If DMAR is
> ready for kvm.git, I will change this macro as following:
> #if defined(CONFIG_X86) || defined(CONFIG_IA64)
> #define KVM_CAP_DEVICE_ASSIGNMENT 17
> #endif

Yes, that's what I meant.

  reply	other threads:[~2008-10-03  7:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  5:26 [PATCH 2/8]kvm: Moving device_assignment logic to kvm_main.c Zhang, Xiantao
2008-10-03  7:09 ` Amit Shah
2008-10-03  7:32   ` Zhang, Xiantao
2008-10-03  7:42     ` Amit Shah [this message]
2008-10-03 14:04       ` Zhang, Xiantao
2008-10-03 14:12         ` Amit Shah
2008-10-05  9:39     ` Avi Kivity
2008-10-06  3:15       ` Zhang, Xiantao
2008-10-07 13:16     ` Avi Kivity
2008-10-07 23:52       ` 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=200810031312.52056.amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm-ia64@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@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 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).