From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tamas@tklengyel.com>, Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH 2/2] vm_event: Add altp2m info to HVM events as well
Date: Wed, 6 Jan 2016 11:48:24 +0000 [thread overview]
Message-ID: <568CFF08.2050808@citrix.com> (raw)
In-Reply-To: <CABfawhkVUccNKxQ=ptfswsnwqhJgWQ8q+aYQH4No3mb7LTVt=A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
On 06/01/16 11:42, Tamas K Lengyel wrote:
>
>
> On Wed, Jan 6, 2016 at 12:32 PM, Jan Beulich <JBeulich@suse.com
> <mailto:JBeulich@suse.com>> wrote:
>
> >>> On 23.12.15 at 15:53, <tamas@tklengyel.com <mailto:tamas@tklengyel.com>> wrote:
> > @@ -83,6 +84,12 @@ static int hvm_event_traps(uint8_t sync,
> vm_event_request_t *req)
> > vm_event_vcpu_pause(curr);
> > }
> >
> > + if ( altp2m_active(currd) )
> > + {
> > + req->flags |= VM_EVENT_FLAG_ALTERNATE_P2M;
> > + req->altp2m_idx = vcpu_altp2m(curr).p2midx;
> > + }
>
> So far this info was provided just for MEM_ACCESS events. Now
> you provide it for a few more ones, but wouldn't this then better
> be supplied for all of them, namely also the other two MEM ones?
>
>
> AFAIK altp2m is currently incompatible with sharing. I'm not 100% sure
> but I think it's also incompatible with paging.
I don't think they are strictly incompatible; I don't see a technical
reason preventing some development work to make them function together.
Whether this happens or not is a very different matter.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2787 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-06 11:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 14:53 [PATCH 1/2] vm_event: sync domctl Tamas K Lengyel
2015-12-23 14:53 ` [PATCH 2/2] vm_event: Add altp2m info to HVM events as well Tamas K Lengyel
2015-12-23 15:42 ` Razvan Cojocaru
2015-12-23 17:18 ` Andrew Cooper
2016-01-06 11:32 ` Jan Beulich
2016-01-06 11:42 ` Tamas K Lengyel
2016-01-06 11:48 ` Andrew Cooper [this message]
2016-01-06 11:50 ` Tamas K Lengyel
2016-01-12 10:21 ` Jan Beulich
2016-01-12 12:13 ` Tamas K Lengyel
2015-12-23 15:41 ` [PATCH 1/2] vm_event: sync domctl Razvan Cojocaru
2015-12-23 17:17 ` Andrew Cooper
2015-12-23 18:11 ` Tamas K Lengyel
2015-12-23 19:11 ` Razvan Cojocaru
2015-12-23 19:14 ` Andrew Cooper
2015-12-23 20:55 ` Tamas K Lengyel
2015-12-23 21:06 ` Tamas K Lengyel
2015-12-23 21:13 ` Andrew Cooper
2016-01-06 15:48 ` Ian Campbell
2016-01-06 18:29 ` Tamas K Lengyel
2016-01-07 9:58 ` Ian Campbell
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=568CFF08.2050808@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.com \
--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 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).