All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v9 1/9] xen/x86: set the vPMU interface based on the presence of a lapic
Date: Mon, 30 Nov 2015 15:28:30 -0500	[thread overview]
Message-ID: <565CB16E.20307@oracle.com> (raw)
In-Reply-To: <1448631785-11402-2-git-send-email-roger.pau@citrix.com>

On 11/27/2015 08:42 AM, Roger Pau Monne wrote:
> Instead of choosing the interface to expose to guests based on the guest
> type, do it based on whether the guest has an emulated local apic or not.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Acked-by: Jan Beulich <jbeulich@suse.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> Changes since v8:
>   - Don't add the xenpmu hypercalls to the HVM hypercall table (yet).

Without having the hypercalls available to HVMlite (?) guests these 
changes, except possibly those in vmx.c/svm.c, are somewhat pointless 
since we never reach patched code.

I understand desire not to increase size of hypercall tables which we 
want to eventually get rid of but is it really worth doing (or rather 
not doing) at the cost of not including useful functionality?


-boris



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-11-30 20:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 13:42 [PATCH v9 0/9] Introduce HVM without dm and new boot ABI Roger Pau Monne
2015-11-27 13:42 ` [PATCH v9 1/9] xen/x86: set the vPMU interface based on the presence of a lapic Roger Pau Monne
2015-11-30 20:28   ` Boris Ostrovsky [this message]
2015-12-01 12:59     ` Jan Beulich
2015-11-27 13:42 ` [PATCH v9 2/9] xen/x86: make sure the HVM callback vector is correctly set Roger Pau Monne
2015-12-02 16:56   ` Jan Beulich
2015-11-27 13:42 ` [PATCH v9 3/9] xen/x86: allow disabling all emulated devices inside of Xen Roger Pau Monne
2015-11-27 13:43 ` [PATCH v9 4/9] libxc: allow creating domains without emulated devices Roger Pau Monne
2015-11-27 13:43 ` [PATCH v9 5/9] xen/x86: allow HVM guests to use hypercalls to bring up vCPUs Roger Pau Monne
2015-11-30 12:06   ` Julien Grall
2015-12-03 14:20   ` Jan Beulich
2015-11-27 13:43 ` [PATCH v9 6/9] libxc/xen: introduce a start info structure for HVMlite guests Roger Pau Monne
2015-11-30 10:40   ` Jan Beulich
2015-11-27 13:43 ` [PATCH v9 7/9] libxc: switch xc_dom_elfloader to be used with HVMlite domains Roger Pau Monne
2015-11-27 13:43 ` [PATCH v9 8/9] libxl: allow the creation of HVM domains without a device model Roger Pau Monne
2015-11-27 13:43 ` [PATCH v9 9/9] libxl: add support for migrating HVM guests " Roger Pau Monne
2015-11-27 13:55   ` Andrew Cooper
2015-11-27 15:04     ` Roger Pau Monné
2015-11-27 15:11   ` Wei Liu
2015-12-02 20:47 ` [PATCH v9 0/9] Introduce HVM without dm and new boot ABI Boris Ostrovsky

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=565CB16E.20307@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.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 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.