On Tue, 2015-08-25 at 10:40 +0100, Wei Liu wrote:
> On Sun, Aug 23, 2015 at 05:33:17PM +0800, Yu Zhang wrote:
> > Currently in ioreq server, guest write-protected ram pages are
> > tracked in the same rangeset with device mmio resources. Yet
> > unlike device mmio, which can be in big chunks, the
>>> On 23.08.15 at 11:33, wrote:
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -938,8 +938,9 @@ static int hvm_ioreq_server_alloc_rangesets(struct
> hvm_ioreq_server *s,
>
> rc = asprintf(, "ioreq_server %d %s", s->id,
>
On 28.08.15 at 05:11, yu.c.zh...@linux.intel.com wrote:
To other maintainers, do you have any question or suggestion?
I certainly intend to get to reviewing these patches, but my originally
huge backlog hasn't shrunk enough yet.
Jan
___
Xen-devel
On 8/28/2015 4:38 PM, Jan Beulich wrote:
On 28.08.15 at 05:11, yu.c.zh...@linux.intel.com wrote:
To other maintainers, do you have any question or suggestion?
I certainly intend to get to reviewing these patches, but my originally
huge backlog hasn't shrunk enough yet.
Jan
Thanks for
On 8/25/2015 5:40 PM, Wei Liu wrote:
On Sun, Aug 23, 2015 at 05:33:17PM +0800, Yu Zhang wrote:
Currently in ioreq server, guest write-protected ram pages are
tracked in the same rangeset with device mmio resources. Yet
unlike device mmio, which can be in big chunks, the guest write-
protected
On Sun, Aug 23, 2015 at 05:33:17PM +0800, Yu Zhang wrote:
Currently in ioreq server, guest write-protected ram pages are
tracked in the same rangeset with device mmio resources. Yet
unlike device mmio, which can be in big chunks, the guest write-
protected pages may be discrete ranges with 4K
Currently in ioreq server, guest write-protected ram pages are
tracked in the same rangeset with device mmio resources. Yet
unlike device mmio, which can be in big chunks, the guest write-
protected pages may be discrete ranges with 4K bytes each. This
patch uses a seperate rangeset for the guest