From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/3] xen/shadow: fix shadow_track_dirty_vram to work on hvm guests
Date: Wed, 6 May 2015 17:12:38 +0200 [thread overview]
Message-ID: <554A2F66.2000905@citrix.com> (raw)
In-Reply-To: <552D22920200007800071E4B@mail.emea.novell.com>
El 14/04/15 a les 14.22, Jan Beulich ha escrit:
>>>> On 10.04.15 at 19:29, <roger.pau@citrix.com> wrote:
>> Modify shadow_track_dirty_vram to use a local buffer and then flush to the
>> guest without the paging_lock held. This is modeled after
>> hap_track_dirty_vram.
>
> And hence introduces the same issue: The HVMOP_track_dirty_vram
> handler explicitly allows for up to 1Gb of VRAM, yet here you
> effectively limit things to 128Mb (one page worth of bits each taking
> care of one guest page) considering heavily fragmented memory.
Where does this limitation come from? We allocate a temporary bitmap
that has enough size to accommodate for the number of entries passed to
the function in nr.
I guess there's some limitation I'm not seeing.
Roger.
next prev parent reply other threads:[~2015-05-06 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 17:29 [PATCH v3 0/3] xen/pvh: enable migration on PVH Dom0 Roger Pau Monne
2015-04-10 17:29 ` [PATCH v3 1/3] xen/pvh: enable mmu_update hypercall Roger Pau Monne
2015-04-14 11:55 ` Jan Beulich
2015-04-14 12:03 ` Roger Pau Monné
2015-04-14 13:10 ` Andrew Cooper
2015-04-16 9:04 ` Tim Deegan
2015-04-10 17:29 ` [PATCH v3 2/3] xen/shadow: fix shadow_track_dirty_vram to work on hvm guests Roger Pau Monne
2015-04-14 12:22 ` Jan Beulich
2015-05-06 15:12 ` Roger Pau Monné [this message]
2015-05-06 15:41 ` Jan Beulich
2015-04-10 17:29 ` [PATCH v3 3/3] xen: rework paging_log_dirty_op to work with " Roger Pau Monne
2015-04-11 9:27 ` Roger Pau Monné
2015-04-14 12:14 ` Jan Beulich
2015-04-16 9:11 ` Tim Deegan
2015-04-16 9:49 ` Jan Beulich
2015-05-06 11:55 ` Roger Pau Monné
2015-05-06 12:10 ` Jan Beulich
2015-05-06 12:32 ` Roger Pau Monné
2015-05-06 12:39 ` Jan Beulich
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=554A2F66.2000905@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.