All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>, Liu Yi L <yi.l.liu@intel.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v2 0/2] iommu/vt-d: Some misc tweaks in SVA
Date: Tue, 26 Jan 2021 16:07:28 +0800	[thread overview]
Message-ID: <20210126080730.2232859-1-baolu.lu@linux.intel.com> (raw)

This includes some misc tweaks in the VT-d SVA implementation. I will
plan them for v5.12 if no objections.

Change log:
v1->v2:
  - v1:
    https://lore.kernel.org/linux-iommu/20210121014505.1659166-1-baolu.lu@linux.intel.com/
  - Keep the logic of clearing PRO sane
  - Drop the device outstanding PRQ number patch. Need more test and
    will repost later. 

Best regards,
baolu

Lu Baolu (2):
  iommu/vt-d: Clear PRQ overflow only when PRQ is empty
  iommu/vt-d: Use INVALID response code instead of FAILURE

 drivers/iommu/intel/svm.c | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Ashok Raj <ashok.raj@intel.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [PATCH v2 0/2] iommu/vt-d: Some misc tweaks in SVA
Date: Tue, 26 Jan 2021 16:07:28 +0800	[thread overview]
Message-ID: <20210126080730.2232859-1-baolu.lu@linux.intel.com> (raw)

This includes some misc tweaks in the VT-d SVA implementation. I will
plan them for v5.12 if no objections.

Change log:
v1->v2:
  - v1:
    https://lore.kernel.org/linux-iommu/20210121014505.1659166-1-baolu.lu@linux.intel.com/
  - Keep the logic of clearing PRO sane
  - Drop the device outstanding PRQ number patch. Need more test and
    will repost later. 

Best regards,
baolu

Lu Baolu (2):
  iommu/vt-d: Clear PRQ overflow only when PRQ is empty
  iommu/vt-d: Use INVALID response code instead of FAILURE

 drivers/iommu/intel/svm.c | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

-- 
2.25.1

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2021-01-26 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  8:07 Lu Baolu [this message]
2021-01-26  8:07 ` [PATCH v2 0/2] iommu/vt-d: Some misc tweaks in SVA Lu Baolu
2021-01-26  8:07 ` [PATCH v2 1/2] iommu/vt-d: Clear PRQ overflow only when PRQ is empty Lu Baolu
2021-01-26  8:07   ` Lu Baolu
2021-01-26  8:07 ` [PATCH v2 2/2] iommu/vt-d: Use INVALID response code instead of FAILURE Lu Baolu
2021-01-26  8:07   ` Lu Baolu
2021-01-29  8:25 ` [PATCH v2 0/2] iommu/vt-d: Some misc tweaks in SVA Joerg Roedel

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=20210126080730.2232859-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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.