All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Shaohua Li <shli@fb.com>
Cc: "Sun, Ning" <ning.sun@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Wei, Gang" <gang.wei@intel.com>,
	"hpa@linux.intel.com" <hpa@linux.intel.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"kernel-team@fb.com" <kernel-team@fb.com>,
	"srihan@fb.com" <srihan@fb.com>,
	"Eydelberg, Alex" <alex.eydelberg@intel.com>
Subject: Re: [RFC] x86/tboot: add an option to disable iommu force on
Date: Tue, 25 Apr 2017 13:02:16 +0200	[thread overview]
Message-ID: <20170425110216.GO5077@suse.de> (raw)
In-Reply-To: <20170424165059.GA65052@MacBook-Pro.local>

On Mon, Apr 24, 2017 at 09:50:59AM -0700, Shaohua Li wrote:
> Hi Joerg,
> 
> Is Ning's answer sufficient to justify merging the patch?

Yes, I will take it if you repost without the RFC tag and when you add
documentation for the new command-line parameter.

I think a kernel-log message about the potential security impact also
makes sense.


	Joerg

      reply	other threads:[~2017-04-25 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 18:37 [RFC] x86/tboot: add an option to disable iommu force on Shaohua Li
2017-03-22 10:49 ` Joerg Roedel
2017-03-22 11:50   ` Shaohua Li
2017-04-03 19:19     ` Shaohua Li
2017-04-07 10:08       ` Joerg Roedel
2017-04-07 21:49         ` Sun, Ning
2017-04-10  4:31           ` Shaohua Li
2017-04-10 21:28             ` Sun, Ning
2017-04-24 16:50               ` Shaohua Li
2017-04-25 11:02                 ` Joerg Roedel [this message]

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=20170425110216.GO5077@suse.de \
    --to=jroedel@suse.de \
    --cc=alex.eydelberg@intel.com \
    --cc=gang.wei@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=ning.sun@intel.com \
    --cc=shli@fb.com \
    --cc=srihan@fb.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.