From: dmkhn@proton.me
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, christopher.w.clark@gmail.com,
dpsmith@apertussolutions.com, michal.orzel@amd.com,
persaur@gmail.com, dmukhin@ford.com
Subject: Re: [XTF PATCH v2 2/2] tests/argo: use event channel to get own domain ID
Date: Thu, 22 May 2025 18:22:41 +0000 [thread overview]
Message-ID: <aC9rbByD7BaRCvV4@kraken> (raw)
In-Reply-To: <850d4bf8-3e98-4aee-9d41-e298be34893a@citrix.com>
On Wed, May 21, 2025 at 10:37:40PM +0100, Andrew Cooper wrote:
> On 21/05/2025 10:18 pm, dmkhn@proton.me wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > The existing argo test depends on xenstore to retrieve the domain ID.
> >
> > Also, test does not perform peer-to-peer communication using Argo hypercall, it
> > communicates with itself.
> >
> > Since xenstore currently runs in dom0, xenstore adds unnecessary dependency on
> > dom0 for the test in x86 QEMU environment.
> >
> > Use event channel to identify the domain ID which eliminates dom0 dependency
> > for the test.
> >
> > Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> > ---
> > Changes since v1:
> > - dropped hack of hardcoding test's own domain ID to 0, reworked getting own
> > domain ID by relying on message channel.
> >
> > Thanks to Michal Orzel and Andrew Cooper for helping with that.
>
> Thanks, although this needs integrating into the pending series I've
> already got. Notably, we want to use the CPUID if it's available.
>
> It also needs to be ahead of the argo test to avoid a bisection hazard.
>
> I'll pick this up and sort things out.
Thank you!
>
> ~Andrew
prev parent reply other threads:[~2025-05-22 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 21:17 [XTF PATCH v2 0/2] xtf: integrate argo test dmkhn
2025-05-21 21:18 ` [XTF PATCH v2 1/2] tests/argo: Add argo test suite dmkhn
2025-05-29 21:45 ` Christopher Clark
2025-05-21 21:18 ` [XTF PATCH v2 2/2] tests/argo: use event channel to get own domain ID dmkhn
2025-05-21 21:37 ` Andrew Cooper
2025-05-22 18:22 ` dmkhn [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=aC9rbByD7BaRCvV4@kraken \
--to=dmkhn@proton.me \
--cc=andrew.cooper3@citrix.com \
--cc=christopher.w.clark@gmail.com \
--cc=dmukhin@ford.com \
--cc=dpsmith@apertussolutions.com \
--cc=michal.orzel@amd.com \
--cc=persaur@gmail.com \
--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.