From: Ian Campbell <ian.campbell@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"Yu, Zhang" <yu.c.zhang@linux.intel.com>,
Wei Liu <wei.liu2@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: [PATCH 3/3] tools: introduce parameter max_ranges.
Date: Wed, 20 Jan 2016 10:16:18 +0000 [thread overview]
Message-ID: <1453284978.26343.29.camel@citrix.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F786138@SHSMSX101.ccr.corp.intel.com>
On Wed, 2016-01-20 at 03:58 +0000, Tian, Kevin wrote:
> > From: Yu, Zhang [mailto:yu.c.zhang@linux.intel.com]
> > Sent: Wednesday, January 20, 2016 11:33 AM
> > > As a feature this write-protection has nothing to be GPU
> > > virtualization specific.
> > > In the future the same mediated pass-through idea used in XenGT may
> > > be
> > > used on other I/O devices which need to shadow some structure w/
> > > requirement
> > > to write-protect guest memory. So it's not good to tie this to either
> > > XenGT
> > > or GTT.
> > >
> > Thank you, Kevin.
> > Well, if this parameter is not supposed to be xengt specific, we do not
> > need to connect it with any xengt flag such as ."vgt=1" or "GVT-g=1".
> > Hence the user will have to configure the max_wp_ram_ranges himself,
> > right?
> >
>
> Not always. The option can be configured manually by the user, or
> automatically set in the code when "vgt=1" is recognized.
Is the latter approach not always sufficient? IOW, if it can be done
automatically, why would the user need to tweak it?
Ian.
next prev parent reply other threads:[~2016-01-20 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 9:27 [PATCH v10 0/3] Refactor ioreq server for better performance Yu Zhang
2016-01-19 9:27 ` [PATCH v10 1/3] Refactor rangeset structure " Yu Zhang
2016-01-19 9:27 ` [PATCH v10 2/3] Differentiate IO/mem resources tracked by ioreq server Yu Zhang
2016-01-19 9:47 ` Paul Durrant
2016-01-19 9:27 ` [PATCH 3/3] tools: introduce parameter max_ranges Yu Zhang
2016-01-19 11:53 ` Wei Liu
2016-01-19 13:54 ` Paul Durrant
2016-01-19 14:37 ` Wei Liu
2016-01-19 14:47 ` Paul Durrant
2016-01-19 15:04 ` Wei Liu
2016-01-19 15:18 ` Ian Campbell
2016-01-20 3:14 ` Tian, Kevin
2016-01-20 3:33 ` Yu, Zhang
2016-01-20 3:58 ` Tian, Kevin
2016-01-20 5:02 ` Yu, Zhang
2016-01-20 10:17 ` Wei Liu
2016-01-20 10:16 ` Ian Campbell [this message]
2016-01-20 10:18 ` Paul Durrant
2016-01-20 11:13 ` Yu, Zhang
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=1453284978.26343.29.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhiyuan.lv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).