All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
	paul@xen.org, Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH for-4.14] mm: fix public declaration of struct xen_mem_acquire_resource
Date: Tue, 23 Jun 2020 17:04:53 +0200	[thread overview]
Message-ID: <044c278b-e0df-e389-b21a-66c7307997c4@suse.com> (raw)
In-Reply-To: <20200623135246.66170-1-roger.pau@citrix.com>

On 23.06.2020 15:52, Roger Pau Monne wrote:
> XENMEM_acquire_resource and it's related structure is currently inside
> a __XEN__ or __XEN_TOOLS__ guarded section to limit it's scope to the
> hypervisor or the toolstack only. This is wrong as the hypercall is
> already being used by the Linux kernel at least, and as such needs to
> be public.

Actually - how does this work for the Linux kernel, seeing

    rc = rcu_lock_remote_domain_by_id(xmar.domid, &d);
    if ( rc )
        return rc;

    rc = xsm_domain_resource_map(XSM_DM_PRIV, d);
    if ( rc )
        goto out;

in the function?

Jan


  parent reply	other threads:[~2020-06-23 15:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 13:52 [PATCH for-4.14] mm: fix public declaration of struct xen_mem_acquire_resource Roger Pau Monne
2020-06-23 13:59 ` Paul Durrant
2020-06-23 14:27 ` Julien Grall
2020-06-23 15:02 ` Jan Beulich
2020-06-23 15:56   ` Roger Pau Monné
2020-06-23 16:18     ` Jan Beulich
2020-06-23 17:26       ` Roger Pau Monné
2020-06-24 10:12         ` Jan Beulich
2020-06-24 13:41           ` Julien Grall
2020-06-24 14:01             ` Jan Beulich
2020-06-25  9:05               ` Roger Pau Monné
2020-06-25 16:10                 ` Roger Pau Monné
2020-06-26 13:40                   ` Jan Beulich
2020-06-26 14:19                     ` Jan Beulich
2020-06-26 15:03                       ` Roger Pau Monné
2020-06-26 15:25                         ` Jan Beulich
2020-06-25  9:24               ` Julien Grall
2020-06-23 15:04 ` Jan Beulich [this message]
2020-06-23 17:32   ` Roger Pau Monné
2020-06-24 10:05     ` Jan Beulich
2020-06-24 10:52       ` Julien Grall
2020-06-24 12:08         ` Jan Beulich
2020-06-24 12:47           ` Julien Grall
2020-06-24 12:52             ` Jan Beulich
2020-06-24 12:53               ` Paul Durrant
2020-06-24 13:07                 ` 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=044c278b-e0df-e389-b21a-66c7307997c4@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien@xen.org \
    --cc=paul@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@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.