From: dmkhn@proton.me
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
anthony.perard@vates.tech, jbeulich@suse.com, julien@xen.org,
michal.orzel@amd.com, roger.pau@citrix.com,
sstabellini@kernel.org, dmukhin@ford.com,
Xen-devel <xen-devel-bounces@lists.xenproject.org>
Subject: Re: [PATCH v10 2/3] xen/domain: update create_dom0() messages
Date: Tue, 22 Jul 2025 23:19:24 +0000 [thread overview]
Message-ID: <aIAceOe9k/PkHqnW@kraken> (raw)
In-Reply-To: <DBE9HJ5W3RUO.2K451XN5JAWG9@amd.com>
On Thu, Jul 17, 2025 at 12:34:56PM +0200, Alejandro Vallejo wrote:
> On Mon Jun 23, 2025 at 8:28 PM CEST, dmkhn wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > Use %pd for domain identification in error/panic messages in create_dom0().
> >
> > No functional change.
> >
> > Signed-off-by: Denis Mukhin <dmukhin@ford.com>
>
> nit below. But with or without that change:
>
> Reviewed-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Thanks
>
> > ---
> > Changes since v9:
> > - new patch
> > ---
> > xen/arch/arm/domain_build.c | 8 ++++----
> > xen/arch/x86/setup.c | 4 ++--
> > 2 files changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> > index 9fa5143eb98c..b59b56636920 100644
> > --- a/xen/arch/arm/domain_build.c
> > +++ b/xen/arch/arm/domain_build.c
> > @@ -2080,17 +2080,17 @@ void __init create_dom0(void)
> >
> > dom0 = domain_create(domid, &dom0_cfg, flags);
> > if ( IS_ERR(dom0) )
> > - panic("Error creating domain 0 (rc = %ld)\n", PTR_ERR(dom0));
> > + panic("Error creating d%d (rc = %ld)\n", domid, PTR_ERR(dom0));
> >
> > if ( llc_coloring_enabled && (rc = dom0_set_llc_colors(dom0)) )
> > - panic("Error initializing LLC coloring for domain 0 (rc = %d)\n", rc);
> > + panic("Error initializing LLC coloring for %pd (rc = %d)\n", dom0, rc);
> >
> > if ( alloc_dom0_vcpu0(dom0) == NULL )
> > - panic("Error creating domain 0 vcpu0\n");
> > + panic("Error creating %pdv0\n", dom0);
> >
> > rc = construct_dom0(dom0);
> > if ( rc )
> > - panic("Could not set up DOM0 guest OS (rc = %d)\n", rc);
> > + panic("Could not set up guest OS for %pd (rc = %d)\n", dom0, rc);
>
> nit: s/guest OS for %pd/%pd guest OS/
Ack
>
> >
> > set_xs_domain(dom0);
> > }
> > diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c
> > index 7adb92d78a18..28bcfd1861d4 100644
> > --- a/xen/arch/x86/setup.c
> > +++ b/xen/arch/x86/setup.c
> > @@ -1080,7 +1080,7 @@ static struct domain *__init create_dom0(struct boot_info *bi)
> >
> > if ( (strlen(acpi_param) == 0) && acpi_disabled )
> > {
> > - printk("ACPI is disabled, notifying Domain 0 (acpi=off)\n");
> > + printk("ACPI is disabled, notifying %pd (acpi=off)\n", d);
> > safe_strcpy(acpi_param, "off");
> > }
> >
> > @@ -1095,7 +1095,7 @@ static struct domain *__init create_dom0(struct boot_info *bi)
> >
> > bd->d = d;
> > if ( construct_dom0(bd) != 0 )
> > - panic("Could not construct domain 0\n");
> > + panic("Could not construct %pd\n", d);
> >
> > bd->cmdline = NULL;
> > xfree(cmdline);
>
next prev parent reply other threads:[~2025-07-22 23:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 18:27 [PATCH v10 0/3] xen/domain: domain ID allocation dmkhn
2025-06-23 18:28 ` [PATCH v10 1/3] xen/domain: unify " dmkhn
2025-06-24 5:58 ` Jan Beulich
2025-07-17 10:27 ` Alejandro Vallejo
2025-07-22 23:17 ` dmkhn
2025-06-23 18:28 ` [PATCH v10 2/3] xen/domain: update create_dom0() messages dmkhn
2025-07-17 10:34 ` Alejandro Vallejo
2025-07-22 23:19 ` dmkhn [this message]
2025-07-17 12:58 ` Grygorii Strashko
2025-07-17 13:03 ` Jan Beulich
2025-07-18 11:20 ` Grygorii Strashko
2025-06-23 18:28 ` [PATCH v10 3/3] xen/domain: use get_initial_domain_id() instead of open-coded 0 dmkhn
2025-06-24 6:07 ` Jan Beulich
2025-07-22 23:24 ` dmkhn
2025-07-17 10:59 ` Alejandro Vallejo
2025-07-22 23:46 ` dmkhn
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=aIAceOe9k/PkHqnW@kraken \
--to=dmkhn@proton.me \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmukhin@ford.com \
--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-bounces@lists.xenproject.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.