; Stefano Stabellini
Subject: Re: [Xen-devel] [PATCH 3/3] tools: introduce parameter
max_ranges.
On Wed, 2016-01-20 at 03:58 +, Tian, Kevin wrote:
From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
Sent: Wednesday, January 20, 2016 11:33 AM
As a feature this write-protection has nothing to be GPU
lini
> Subject: Re: [Xen-devel] [PATCH 3/3] tools: introduce parameter
> max_ranges.
>
> On Wed, 2016-01-20 at 03:58 +, Tian, Kevin wrote:
> > > From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
> > > Sent: Wednesday, January 20, 2016 11:33 AM
> > > &
On Wed, Jan 20, 2016 at 01:02:39PM +0800, Yu, Zhang wrote:
>
>
> On 1/20/2016 11:58 AM, Tian, Kevin wrote:
> >>From: Yu, Zhang [mailto:yu.c.zh...@linux.intel.com]
> >>Sent: Wednesday, January 20, 2016 11:33 AM
> >>>As a feature this write-protection has nothing to be GPU virtualization
> >>>spec
On Wed, 2016-01-20 at 03:58 +, Tian, Kevin wrote:
> > From: Yu, Zhang [mailto:yu.c.zh...@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-throu
On 1/20/2016 11:58 AM, Tian, Kevin wrote:
From: Yu, Zhang [mailto:yu.c.zh...@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
use
> From: Yu, Zhang [mailto:yu.c.zh...@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 whic
On 1/20/2016 11:14 AM, Tian, Kevin wrote:
From: Ian Campbell [mailto:ian.campb...@citrix.com]
Sent: Tuesday, January 19, 2016 11:19 PM
On Tue, 2016-01-19 at 15:04 +, Wei Liu wrote:
This patch doesn't seem to have been CCd to the tools maintainers, adding
Ian too, I think everyone else was
> From: Ian Campbell [mailto:ian.campb...@citrix.com]
> Sent: Tuesday, January 19, 2016 11:19 PM
>
> On Tue, 2016-01-19 at 15:04 +, Wei Liu wrote:
>
> This patch doesn't seem to have been CCd to the tools maintainers, adding
> Ian too, I think everyone else was picked up along the way.
>
> P
On Tue, 2016-01-19 at 15:04 +, Wei Liu wrote:
This patch doesn't seem to have been CCd to the tools maintainers, adding
Ian too, I think everyone else was picked up along the way.
Please use ./scripts/get_maintainers.pl in the future.
> On Tue, Jan 19, 2016 at 02:47:40PM +, Paul Durrant
On Tue, Jan 19, 2016 at 02:47:40PM +, Paul Durrant wrote:
[...]
> > ranges so perhaps the parameter name could be
> > 'max_wp_memory_ranges'?
> > >
> >
> > What does "WP" mean? "Write Protected"?
> >
>
> Yes.
>
> > Is this parameter closely related to IOREQ server? Should it contain
> > "io
6 11:54
> > > To: Yu Zhang
> > > Cc: xen-devel@lists.xen.org; Kevin Tian; Keir (Xen.org); Stefano
> > > Stabellini;
> > > Andrew Cooper; Paul Durrant; zhiyuan...@intel.com; jbeul...@suse.com;
> > > Wei Liu
> > > Subject: Re: [Xen-devel] [PATCH 3/3]
llini;
> > Andrew Cooper; Paul Durrant; zhiyuan...@intel.com; jbeul...@suse.com;
> > Wei Liu
> > Subject: Re: [Xen-devel] [PATCH 3/3] tools: introduce parameter
> > max_ranges.
> >
> > On Tue, Jan 19, 2016 at 05:27:58PM +0800, Yu Zhang wrote:
> > > A new p
Wei Liu
> Subject: Re: [Xen-devel] [PATCH 3/3] tools: introduce parameter
> max_ranges.
>
> On Tue, Jan 19, 2016 at 05:27:58PM +0800, Yu Zhang wrote:
> > A new parameter - max_ranges is added to set the upper limit of ranges
> > to be tracked inside one ioreq server rangeset.
&
On Tue, Jan 19, 2016 at 05:27:58PM +0800, Yu Zhang wrote:
> A new parameter - max_ranges is added to set the upper limit of ranges
> to be tracked inside one ioreq server rangeset.
>
> Ioreq server uses a group of rangesets to track the I/O or memory
> resources to be emulated. The default value o
14 matches
Mail list logo
