All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tian, Kevin" <kevin.tian@intel.com>
To: Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <iwj@xenproject.org>
Subject: RE: [PATCH 0/4][4.15?] VT-d: mostly S3 related corrections
Date: Tue, 23 Mar 2021 08:12:15 +0000	[thread overview]
Message-ID: <MWHPR11MB1886A8DBD8B93A612A1B09958C649@MWHPR11MB1886.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c19fe2b5-b682-374c-d30f-83fb8b367286@suse.com>

> From: Jan Beulich <jbeulich@suse.com>
> Sent: Thursday, March 18, 2021 6:12 PM
> 
> None of these are regressions afaict, so considering how late we are
> in the 4.15 process, I can see reasons to not take any of these. All
> of them are backporting candidates though, imo.
> 
> 1: correct off-by-1 in number-of-IOMMUs check
> 2: leave FECTL write to vtd_resume()
> 3: re-order register restoring in vtd_resume()
> 4: restore flush hooks when disabling qinval
> 

For the series:

Reviewed-by: Kevin Tian <kevin.tian@intel.com>

  parent reply	other threads:[~2021-03-23  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 10:12 [PATCH 0/4][4.15?] VT-d: mostly S3 related corrections Jan Beulich
2021-03-18 10:13 ` [PATCH 1/4][4.15?] VT-d: correct off-by-1 in number-of-IOMMUs check Jan Beulich
2021-03-23 13:31   ` Ian Jackson
2021-03-18 10:13 ` [PATCH 2/4][4.15?] VT-d: leave FECTL write to vtd_resume() Jan Beulich
2021-03-18 10:14 ` [PATCH 3/4][4.15?] VT-d: re-order register restoring in vtd_resume() Jan Beulich
2021-03-18 10:15 ` [PATCH 4/4][4.15?] VT-d: restore flush hooks when disabling qinval Jan Beulich
2021-03-23  8:12 ` Tian, Kevin [this message]
2021-03-23 13:27   ` [PATCH 0/4][4.15?] VT-d: mostly S3 related corrections Jan Beulich
2021-03-23 13:37     ` Ian Jackson
2021-03-30 12:22       ` Jan Beulich

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=MWHPR11MB1886A8DBD8B93A612A1B09958C649@MWHPR11MB1886.namprd11.prod.outlook.com \
    --to=kevin.tian@intel.com \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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 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.