All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Andryuk <jason.andryuk@amd.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Juergen Gross" <jgross@suse.com>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 00/11] xenstored patches from split hardware control
Date: Tue, 26 Aug 2025 12:24:49 -0400	[thread overview]
Message-ID: <74dced99-e48c-4b74-8383-afc353d58dae@amd.com> (raw)
In-Reply-To: <698b0944-0be3-4c04-ba97-a8ef55ebd826@suse.com>

On 2025-08-26 11:53, Jan Beulich wrote:
> On 26.07.2025 01:58, Jason Andryuk wrote:
>> This is a subset of patches focusing on xenstored changes from my split
>> hardware control domain series.
>>
>> It should address the stubdom breakage from the previous series.
>> stubdom was tested in gitlab-ci - xl list shows Domain-0 and Xenstore.
>>
>> "tools/xenstored: Use priv_domid for manual nodes and permission" is an
>> interesting result of looking to rename some internal variables to
>> better align their purpose.
>>
>> Any review or guidance on the approach is appreciated.
>>
>> Jason Andryuk (11):
>>    xen: Add capabilities to get_domain_state
>>    tools/manage: Expose domain capabilities
>>    public/io: xs_wire: Include event channel in interface page
>>    xen/dom0less: store xenstore event channel in page
>>    tools/xenstored: Read event channel from xenstored page
>>    tools/xenstored: Add get_domain_evtchn() to find evtchn
>>    tools/xenstored: Auto-introduce domains
>>    tools/xenstored: Use priv_domid for manual nodes and permission
>>    tools/xenstored: Rename dom0_domid to store_domid
>>    tools/xenstored: Remove stubdom special casing
>>    tools/xenstored: Remove hardcoded implicit path
> 
> To allow more of this to go in, you'll need to chase an ack for patch 4.
> Of course you could also indicate if committing any later changes ahead
> of patch 4 would be possible / sensible.

I re-posted the xenstored changes separately and they have gone in, 
thanks.  Yes, I need to follow up on patch 4.

Thanks,
Jason


      reply	other threads:[~2025-08-26 16:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 23:58 [PATCH v5 00/11] xenstored patches from split hardware control Jason Andryuk
2025-07-25 23:58 ` [PATCH v5 01/11] xen: Add capabilities to get_domain_state Jason Andryuk
2025-07-25 23:58 ` [PATCH v5 02/11] tools/manage: Expose domain capabilities Jason Andryuk
2025-07-30 14:55   ` Anthony PERARD
2025-07-25 23:58 ` [PATCH v5 03/11] public/io: xs_wire: Include event channel in interface page Jason Andryuk
2025-07-25 23:58 ` [PATCH v5 04/11] xen/dom0less: store xenstore event channel in page Jason Andryuk
2025-07-25 23:58 ` [PATCH v5 05/11] tools/xenstored: Read event channel from xenstored page Jason Andryuk
2025-07-25 23:58 ` [PATCH v5 06/11] tools/xenstored: Add get_domain_evtchn() to find evtchn Jason Andryuk
2025-07-28 13:41   ` Jürgen Groß
2025-07-25 23:58 ` [PATCH v5 07/11] tools/xenstored: Auto-introduce domains Jason Andryuk
2025-07-28 13:47   ` Jürgen Groß
2025-07-25 23:58 ` [PATCH v5 08/11] tools/xenstored: Use priv_domid for manual nodes and permission Jason Andryuk
2025-07-28 13:50   ` Jürgen Groß
2025-07-28 13:55   ` Jürgen Groß
2025-07-25 23:58 ` [PATCH v5 09/11] tools/xenstored: Rename dom0_domid to store_domid Jason Andryuk
2025-07-28 13:55   ` Jürgen Groß
2025-07-25 23:58 ` [PATCH v5 10/11] tools/xenstored: Remove stubdom special casing Jason Andryuk
2025-07-28 13:57   ` Jürgen Groß
2025-07-25 23:58 ` [PATCH v5 11/11] tools/xenstored: Remove hardcoded implicit path Jason Andryuk
2025-08-26 15:53 ` [PATCH v5 00/11] xenstored patches from split hardware control Jan Beulich
2025-08-26 16:24   ` Jason Andryuk [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=74dced99-e48c-4b74-8383-afc353d58dae@amd.com \
    --to=jason.andryuk@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@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.