All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: "Henry.Wang@arm.com" <Henry.Wang@arm.com>,
	George Dunlap <George.Dunlap@citrix.com>, Wei Liu <wl@xen.org>,
	Edwin Torok <edvin.torok@citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH for-4.17?] x86/paging: return -EINVAL for paging domctls for dying domains
Date: Thu, 10 Nov 2022 10:02:21 +0100	[thread overview]
Message-ID: <3b97cfcd-e741-c89b-8063-e3f977ab7ef0@suse.com> (raw)
In-Reply-To: <de5c9f07-90f5-a460-f1f7-a6732bbab1df@citrix.com>

On 09.11.2022 17:11, Andrew Cooper wrote:
> On 08/11/2022 11:38, Roger Pau Monne wrote:
>> Like on the Arm side, return -EINVAL when attempting to do a p2m
>> operation on dying domains.
> 
> Honestly, I'd drop the comment about ARM.  "the Arm side" has existed
> for of all of a couple of weeks.
> 
> A far better justification is because almost all other DOMCTLs are
> rejected with -EINVAL against dying domains.

Would you mind supplying data to prove this statement? When looking
at just x86'es arch_do_domctl() I can't see this being the case for
ioport_permission, getpageframeinfo3, hypercall_init, set_address_size,
get_address_size, sendtrigger, bind_pt_irq, unbind_pt_irq,
ioport_mapping, set_ext_vcpucontext, and get_ext_vcpucontext. At which
point I stopped checking further because in the order they appear in
the file these are _all_ except shadow_op and [gs]ethvmcontext*. Am I
overlooking hidden checks of ->is_dying?

Jan


      reply	other threads:[~2022-11-10  9:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 11:38 [PATCH for-4.17?] x86/paging: return -EINVAL for paging domctls for dying domains Roger Pau Monne
2022-11-08 16:14 ` Jan Beulich
2022-11-08 16:43   ` Roger Pau Monné
2022-11-08 17:03     ` Jan Beulich
2022-11-08 17:15       ` Roger Pau Monné
2022-11-09  7:48         ` Jan Beulich
2022-11-09  9:45           ` Edwin Torok
2022-11-09  9:58             ` Jan Beulich
2022-11-09 10:11           ` Roger Pau Monné
2022-11-09 10:23             ` Jan Beulich
2022-11-09 11:36               ` Roger Pau Monné
2022-11-09 12:02                 ` Jan Beulich
2022-11-09 13:22                   ` Roger Pau Monné
2022-11-10  9:03                     ` Jan Beulich
2022-11-08 17:30     ` Edwin Torok
2022-11-09 16:11 ` Andrew Cooper
2022-11-10  9:02   ` Jan Beulich [this message]

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=3b97cfcd-e741-c89b-8063-e3f977ab7ef0@suse.com \
    --to=jbeulich@suse.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Henry.Wang@arm.com \
    --cc=edvin.torok@citrix.com \
    --cc=roger.pau@citrix.com \
    --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.