From: "Jan Beulich" <JBeulich@suse.com>
To: "wei.liu2@citrix.com" <wei.liu2@citrix.com>, Feng Wu <feng.wu@intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Yong Y Wang <yong.y.wang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: Requesting for freeze exception for VT-d posted-interrupts
Date: Mon, 13 Jul 2015 10:05:29 +0100 [thread overview]
Message-ID: <55A39B790200007800090091@mail.emea.novell.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F002608531@SHSMSX104.ccr.corp.intel.com>
>>> On 13.07.15 at 08:55, <feng.wu@intel.com> wrote:
> There are two main outstanding issues so far:
> 1. Jan's security concern. I have proposed some solutions but Jan still has
> some problems with my proposals. It would be great if Jan can give a clear
> proposal so that we can discuss and keep making progress.
My proposal was quite clear: The functionality remains experimental,
default off until you can come up with a satisfactory model here.
Giving the impression that I'm the one to propose a model is simply
inadequate: You want the functionality in, so it's primarily you who
should find an implementation that's free of (latent) security issues.
While in general other maintainers may help with this, implying that
if they can't suggest a suitable model code with recognized potential
for security problems can go in _and_ become supported is wrong.
Jan
next prev parent reply other threads:[~2015-07-13 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:55 Requesting for freeze exception for VT-d posted-interrupts Wu, Feng
2015-07-13 9:05 ` Jan Beulich [this message]
2015-07-13 11:00 ` Wei Liu
2015-07-14 5:51 ` Wu, Feng
2015-07-14 9:21 ` Wei Liu
2015-07-14 10:09 ` Jan Beulich
2015-07-14 14:17 ` Wei Liu
2015-07-14 14:46 ` Jan Beulich
2015-07-14 15:02 ` Wei Liu
2015-07-14 16:01 ` Jan Beulich
2015-07-15 15:46 ` Wei Liu
2015-07-15 22:48 ` Wu, Feng
2015-07-17 9:28 ` Wei Liu
2015-07-13 15:38 ` Dario Faggioli
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=55A39B790200007800090091@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=feng.wu@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
--cc=yong.y.wang@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.