xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH 5/5] tools/libxenctrl: use new xenforeignmemory API to seed grant table
Date: Fri, 4 Aug 2017 15:39:09 +0200	[thread overview]
Message-ID: <629f050c-0584-5e12-e97c-73e8fe6edab1@suse.com> (raw)
In-Reply-To: <20170804132158.yq3f6o2otjgufslw@citrix.com>

On 04/08/17 15:21, Wei Liu wrote:
> On Fri, Aug 04, 2017 at 03:02:03PM +0200, Marek Marczykowski-Górecki wrote:
>> On Fri, Aug 04, 2017 at 01:26:21PM +0100, Wei Liu wrote:
>>> On Wed, Aug 02, 2017 at 10:59:49AM +0100, Paul Durrant wrote:
>>>> A previous patch added support for priv-mapping guest resources directly
>>>> (rather than having to foreign-map, which requires P2M modification for
>>>> HVM guests).
>>>>
>>>> This patch makes use of the new API to seed the guest grant table unless
>>>> the underlying infrastructure (i.e. privcmd) doesn't support it, in which
>>>> case the old scheme is used.
>>>>
>>>
>>> The code mostly looks fine.
>>>
>>> What's the benefit of doing this?
>>
>> Also, I see changed signature of xc_dom_gnttab_seed (it got is_hvm
>> parameter). Wei, what is the policy for backward incompatible libxc API
>> changes?
> 
> libxc isn't stable, so functions might get deleted / updated at any
> point.
> 
> Most libxc functions are quite simple and are quite "close" to the
> hypervisor.
> 
> The non-trivial functions I know of are VMI related ones but I think
> users in that area already have the right expectation.
> 
> An important user of unstable libxc APIs is QEMU. It probes for specific
> functions in the configure script to handle compatibility issues.

Right now qemu can just use the version of libxc instead of doing it via
tests. :-)


Juergen

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

  reply	other threads:[~2017-08-04 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  9:59 [PATCH 0/5] x86: guest resource mepping Paul Durrant
2017-08-02  9:59 ` [PATCH 1/5] [x86|arm]: remove code duplication Paul Durrant
2017-08-02  9:59 ` [PATCH 2/5] x86/mm: allow a privileged PV domain to map guest mfns Paul Durrant
2017-08-02  9:59 ` [PATCH 3/5] x86/mm: add HYPERVISOR_memory_op to acquire guest resources Paul Durrant
2017-08-02  9:59 ` [PATCH 4/5] tools/libxenforeignmemory: add support for resource mapping Paul Durrant
2017-08-04 12:15   ` Wei Liu
2017-08-07 12:41     ` Paul Durrant
2017-08-02  9:59 ` [PATCH 5/5] tools/libxenctrl: use new xenforeignmemory API to seed grant table Paul Durrant
2017-08-04 12:26   ` Wei Liu
2017-08-04 13:02     ` Marek Marczykowski-Górecki
2017-08-04 13:21       ` Wei Liu
2017-08-04 13:39         ` Juergen Gross [this message]
2017-08-07 12:36       ` Paul Durrant
2017-08-07 12:35     ` Paul Durrant

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=629f050c-0584-5e12-e97c-73e8fe6edab1@suse.com \
    --to=jgross@suse.com \
    --cc=xen-devel@lists.xen.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).