All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Han, Weidong" <weidong.han@intel.com>
To: 'Amit Shah' <amit.shah@redhat.com>,
	"Huang, Wei W" <wei.w.huang@intel.com>
Cc: 'kvm' <kvm@vger.kernel.org>
Subject: RE: [PATCH] kvm: userspace: change vtd.o to iommu.o in Kbuild
Date: Fri, 9 Jan 2009 09:36:54 +0800	[thread overview]
Message-ID: <715D42877B251141A38726ABF5CABF2C018E8FEAB4@pdsmsx503.ccr.corp.intel.com> (raw)
In-Reply-To: <20090108120913.GA16792@amit-x200.pnq.redhat.com>

Amit Shah wrote:
> On Thu, Jan 08, 2009 at 03:27:12PM +0800, Huang, Wei W wrote:
>> vtd.c has been renamed to iommu.c, need to change it in Kbuild
>> accordingly. 
>> 
>> Signed-off-by: Wei Huang <wei.w.huang@intel.com>
>> ---
>>  kernel/x86/Kbuild |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> 
>> diff --git a/kernel/x86/Kbuild b/kernel/x86/Kbuild
>> index c4723b1..48339b4 100644
>> --- a/kernel/x86/Kbuild
>> +++ b/kernel/x86/Kbuild
>> @@ -10,7 +10,7 @@ ifeq ($(EXT_CONFIG_KVM_TRACE),y)
>>  kvm-objs += kvm_trace.o
>>  endif
>>  ifeq ($(CONFIG_DMAR),y)
>> -kvm-objs += vtd.o
>> +kvm-objs += iommu.o
> 
> This won't be able to build an older kernel.
> 

Because IOMMU APIs were changed in kernel, it needs external module to support older kernel.

Regards,
Weidong

> Amit


  reply	other threads:[~2009-01-09  1:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  7:27 [PATCH] kvm: userspace: change vtd.o to iommu.o in Kbuild Huang, Wei W
2009-01-08 12:09 ` Amit Shah
2009-01-09  1:36   ` Han, Weidong [this message]
2009-01-09  1:40   ` Zhang, Xiantao
2009-01-09  7:05     ` [PATCH] kvm: userspace: change vtd.o to iommu.o in Kbuild for IA64 Huang, Wei W
2009-01-13  7:31 [PATCH] kvm: userspace: change vtd.o to iommu.o in Kbuild Zheng, Shaohui

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=715D42877B251141A38726ABF5CABF2C018E8FEAB4@pdsmsx503.ccr.corp.intel.com \
    --to=weidong.han@intel.com \
    --cc=amit.shah@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=wei.w.huang@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.