public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rodel, Jorg" <jroedel@suse.de>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Baolu Lu <baolu.lu@linux.intel.com>,
	Steve Wahl <steve.wahl@hpe.com>,
	Kyung Min Park <kyung.min.park@intel.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Will Deacon <will@kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	Mike Travis <mike.travis@hpe.com>,
	Dimitri Sivanich <sivanich@hpe.com>,
	"Anderson, Russ" <russ.anderson@hpe.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/vt-d: Increase DMAR_UNITS_SUPPORTED
Date: Fri, 6 May 2022 09:10:53 +0200	[thread overview]
Message-ID: <YnTJ/YqQpru3YPC+@suse.de> (raw)
In-Reply-To: <BN9PR11MB5276F4D5F8AD33293233B9AB8CC59@BN9PR11MB5276.namprd11.prod.outlook.com>

On Fri, May 06, 2022 at 06:49:43AM +0000, Tian, Kevin wrote:
> another nit: dmar is intel specific thus CONFIG_X86 is always true.

There are Itanium systems which have DMAR units. Is that no longer
supported?

Regards,

-- 
Jörg Rödel
jroedel@suse.de

SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
 
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


  reply	other threads:[~2022-05-06  7:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 19:46 [PATCH] iommu/vt-d: Increase DMAR_UNITS_SUPPORTED Steve Wahl
2022-05-06  5:57 ` Baolu Lu
2022-05-06  6:49   ` Tian, Kevin
2022-05-06  7:10     ` Rodel, Jorg [this message]
2022-05-06  7:47       ` Tian, Kevin
2022-05-06  7:16     ` David Woodhouse
2022-05-06  8:12       ` Tian, Kevin
2022-05-06 15:26         ` Steve Wahl
2022-05-10  1:16           ` Tian, Kevin
2022-05-10 19:06             ` Steve Wahl
2022-05-11  3:36               ` Tian, Kevin
2022-05-12 15:13 ` [PATCH v2] iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting Steve Wahl
2022-05-12 23:12   ` Steve Wahl
2022-05-13  2:09     ` Baolu Lu
2022-05-18 19:58       ` Steve Wahl
2022-05-23  6:43         ` Tian, Kevin
2022-06-13 20:38   ` Jerry Snitselaar
2022-06-14  1:33     ` Baolu Lu
2022-06-13 20:57   ` Jerry Snitselaar
2022-06-14  1:36     ` Baolu Lu
2022-06-14  1:44       ` Jerry Snitselaar
2022-06-14  1:51         ` Baolu Lu
2022-06-14  1:54           ` Jerry Snitselaar
2022-06-14  2:21             ` Baolu Lu
2022-06-14 16:45               ` Steve Wahl
2022-06-14 19:01                 ` Jerry Snitselaar
2022-06-14 21:12                   ` Steve Wahl
2022-06-15  1:38                     ` Baolu Lu
2022-06-15 15:02                       ` Steve Wahl
2022-06-15 18:36                       ` [PATCH v3] " Steve Wahl
2022-06-15 18:39                         ` Jerry Snitselaar
2022-06-22 14:52                         ` Baolu Lu
2022-06-22 15:05                           ` Jerry Snitselaar
2022-06-22 15:11                             ` Steve Wahl
2022-06-23  2:29                             ` Baolu Lu
2022-06-23  2:51                               ` Jerry Snitselaar
2022-06-23  3:38                                 ` Baolu Lu

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=YnTJ/YqQpru3YPC+@suse.de \
    --to=jroedel@suse.de \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=kevin.tian@intel.com \
    --cc=kyung.min.park@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=russ.anderson@hpe.com \
    --cc=sivanich@hpe.com \
    --cc=steve.wahl@hpe.com \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox