mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fenghua Yu <fenghua.yu@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Ingo Molnar <mingo@elte.hu>, Avi Kivity <avi@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-ia64@vger.kernel.org
Subject: [PATCH 0/2]Add Variable Page Size and IA64 Support in Intel IOMMU
Date: Wed, 1 Oct 2008 09:56:06 -0700	[thread overview]
Message-ID: <20081001165606.GA21279@linux-os.sc.intel.com> (raw)


The following two patches (Intel IOMMU generic patch and ia64 specific patch) together enable Intel IOMMU on IA64 platform. They are applied cleanly on the latest linux-next tree which contains Intel IOMMU interrupt remapping and VT-d driver KVM support code.

If applying only the generic patch on x86-64 kernel, x86-64 IOMMU is working fine, i.e. the generic patch doesn't have compilation and functionality impact on x86-64 IOMMU. If applying only the ia64 specific patch on ia64 kernel, ia64 is working as non-IOMMU/swiotlb case. If applying both of the patches and set CONFIG_DMAR=y, ia64 IOMMU is working.

Thanks.

-Fenghua

             reply	other threads:[~2008-10-01 16:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 16:56 Fenghua Yu [this message]
2008-10-03 15:50 ` Bjorn Helgaas
2008-10-06 19:44   ` Yu, Fenghua
2008-10-07  0:01 ` [PATCH V2 0/2] Add " Fenghua Yu
2009-02-11 18:26 ` [PATCH]iwlan dma mapping read and write changes Fenghua Yu
2009-02-11 18:35   ` Bhavesh Davda
2009-02-11 19:29     ` Yu, Fenghua
2009-02-11 18:59   ` Chris Wright
2009-02-11 21:27   ` Winkler, Tomas
2009-02-11 21:33     ` Johannes Berg
2009-02-11 21:41       ` Winkler, Tomas
2009-02-11 21:47         ` Johannes Berg
2009-02-11 21:50           ` Johannes Berg
2009-02-11 22:10             ` Winkler, Tomas
2009-02-11 22:13               ` Yu, Fenghua
2009-02-11 22:13               ` David Woodhouse
2009-02-12 13:42                 ` Winkler, Tomas

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=20081001165606.GA21279@linux-os.sc.intel.com \
    --to=fenghua.yu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tony.luck@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
Powered by JetHome