All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH for-4.22? 2/9] domctl: move XEN_DOMCTL_irq_permission handling to x86 code
Date: Tue, 16 Jun 2026 09:22:47 +0200	[thread overview]
Message-ID: <e0d6f8a1-749a-4e23-bd09-1665be6e431d@gmail.com> (raw)
In-Reply-To: <96a089dc-a0dd-4f40-b1e4-5573202bf532@suse.com>



On 6/15/26 4:12 PM, Jan Beulich wrote:
> HAS_PIRQ is selected by x86 only, and that's expected to remain that way.
> Avoid the #ifdef needed by moving the logic to arch_do_domctl(). Leverage
> "currd" being available as a local variable there while doing so.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
> 

Release-Acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>

Thanks.

~ Oleksii


  reply	other threads:[~2026-06-16  7:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15 14:11 [PATCH for-4.22? 0/9] domctl: XSA-492 and -491 follow-on Jan Beulich
2026-06-15 14:12 ` [PATCH for-4.22? 1/9] sched: introduce specialization of "running only" vcpu_runstate_get() Jan Beulich
2026-06-16  8:41   ` Roger Pau Monné
2026-06-16  8:48     ` Jan Beulich
2026-06-16  9:21   ` Jürgen Groß
2026-06-15 14:12 ` [PATCH for-4.22? 2/9] domctl: move XEN_DOMCTL_irq_permission handling to x86 code Jan Beulich
2026-06-16  7:22   ` Oleksii Kurochko [this message]
2026-06-15 14:13 ` [PATCH for-4.22? 3/9] domctl: rename a label Jan Beulich
2026-06-16  7:23   ` Oleksii Kurochko
2026-06-16  8:43   ` Roger Pau Monné
2026-06-15 14:13 ` [PATCH for-4.22? 4/9] domctl: error code adjustment for unpriv callers Jan Beulich
2026-06-16  7:27   ` Oleksii Kurochko
2026-06-15 14:13 ` [PATCH for-4.22? 5/9] domctl/XSM: avoid XSM_OTHER with xsm_domctl() Jan Beulich
2026-06-15 20:57   ` Daniel P. Smith
2026-06-15 14:15 ` [PATCH for-4.22? 6/9] domctl: handle XEN_DOMCTL_getvcpuinfo without acquiring domctl lock Jan Beulich
2026-06-16  8:56   ` Roger Pau Monné
2026-06-16  9:08     ` Jan Beulich
2026-06-15 14:15 ` [PATCH for-4.22? 7/9] domctl: restrict permission check for XEN_DOMCTL_memory_mapping's remove form Jan Beulich
2026-06-16  9:08   ` Roger Pau Monné
2026-06-16  9:51     ` Jan Beulich
2026-06-16 10:06       ` Roger Pau Monné
2026-06-15 14:16 ` [PATCH for-4.22? 8/9] x86/domctl: don't imply I/O port permissions from I/O port mapping Jan Beulich
2026-06-16  9:21   ` Roger Pau Monné
2026-06-16  9:36     ` Jan Beulich
2026-06-16 10:09       ` Roger Pau Monné
2026-06-15 14:16 ` [PATCH for-4.22? 9/9] x86/HVM: more checking for XEN_DOMCTL_ioport_mapping Jan Beulich
2026-06-16 10:01   ` Roger Pau Monné
2026-06-16 10: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=e0d6f8a1-749a-4e23-bd09-1665be6e431d@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.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.