All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: mingo@elte.hu, dwmw2@infradead.org, jbarnes@virtuousgeek.org
Cc: youquan.song@intel.com, suresh.b.siddha@intel.com,
	linux-kernel@vger.kernel.org
Subject: [patch 0/4] dmar: queued invalidation patches
Date: Thu, 16 Oct 2008 16:31:53 -0700	[thread overview]
Message-ID: <20081016233153.093366000@linux-os.sc.intel.com> (raw)

Reposting the patchset posted earlier on Oct 8th. This time against Linus's git.

As this patchset removes a temporary quirk (disabling dma-remapping
when intr-remapping is enabled) we would like to see it go in to Linus tree
in this merge window. I am not sure if David is ready with his iommu
git tree setup. As Ingo pushed the original pieces, I am ok with Ingo
picking this up and pushing it to Linus. Either way, I am fine and would
like to see go into some subsystem tree and to Linus before the merge window
is closed. Thanks.
---

This patchset enables queued invalidation for DMA-remapping. And as such
removes the quirk from the x2apic/interrupt-remapping patchset which
disables dma-remapping while enabling interrupt-remapping.

Patches are on top of -tip tree because of its interaction with
x2apic/interrupt-remapping patches in tip.

Signed-off-by: Youquan Song <youquan.song@intel.com>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
-- 


             reply	other threads:[~2008-10-16 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 23:31 Suresh Siddha [this message]
2008-10-16 23:31 ` [patch 1/4] dmar: use spin_lock_irqsave() in qi_submit_sync() Suresh Siddha
2008-10-16 23:31 ` [patch 2/4] dmar: context cache and IOTLB invalidation using queued invalidation Suresh Siddha
2008-10-16 23:31 ` [patch 3/4] dmar: Use queued invalidation interface for IOTLB and context invalidation Suresh Siddha
2008-10-16 23:31 ` [patch 4/4] dmar: remove the quirk which disables dma-remapping when intr-remapping enabled Suresh Siddha

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=20081016233153.093366000@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=youquan.song@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.