From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Kevin Tian" <kevin.tian@intel.com>
Subject: Re: [PATCH 2/6] VT-d: split domid map cleanup check into a function
Date: Fri, 12 Nov 2021 13:31:37 +0100 [thread overview]
Message-ID: <YY5eqQykvDD8CVmT@Air-de-Roger> (raw)
In-Reply-To: <57c32156-369c-a92a-ecc0-fc4b890eb05c@suse.com>
On Fri, Nov 12, 2021 at 10:48:19AM +0100, Jan Beulich wrote:
> This logic will want invoking from elsewhere.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Might be worth to explicitly note this is a non functional change.
Thanks, Roger.
next prev parent reply other threads:[~2021-11-12 12:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 9:46 [PATCH 0/6] VT-d: domain ID mapping improvements Jan Beulich
2021-11-12 9:47 ` [PATCH 1/6] VT-d: properly reserve DID 0 for caching mode IOMMUs Jan Beulich
2021-11-12 11:23 ` Roger Pau Monné
2021-11-12 12:07 ` Jan Beulich
2021-11-12 12:19 ` Roger Pau Monné
2021-11-15 5:13 ` Tian, Kevin
2021-11-12 12:21 ` Roger Pau Monné
2021-11-15 5:13 ` Tian, Kevin
2021-11-12 9:48 ` [PATCH 2/6] VT-d: split domid map cleanup check into a function Jan Beulich
2021-11-12 12:31 ` Roger Pau Monné [this message]
2021-11-15 5:16 ` Tian, Kevin
2021-11-12 9:48 ` [PATCH 3/6] VT-d: don't leak domid mapping on error path Jan Beulich
2021-11-12 13:42 ` Roger Pau Monné
2021-11-12 13:45 ` Jan Beulich
2021-11-12 14:35 ` Roger Pau Monné
2021-11-15 9:32 ` Jan Beulich
2021-11-15 5:21 ` Tian, Kevin
2021-11-12 9:49 ` [PATCH 4/6] VT-d: tidy domid map handling Jan Beulich
2021-11-15 5:51 ` Tian, Kevin
2021-11-12 9:49 ` [PATCH 5/6] VT-d: introduce helper to convert DID to domid_t Jan Beulich
2021-11-15 5:54 ` Tian, Kevin
2021-11-12 9:50 ` [PATCH 6/6] VT-d: avoid allocating domid_{bit,}map[] when possible Jan Beulich
2021-11-15 6:18 ` Tian, Kevin
2021-11-15 9:37 ` 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=YY5eqQykvDD8CVmT@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.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.