All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] x86/msr: add log messages to MSR state load error paths
Date: Tue, 8 Oct 2024 14:41:56 +0200	[thread overview]
Message-ID: <24ac3cd7-5c49-49d2-9a74-9e8572c62dba@suse.com> (raw)
In-Reply-To: <20241008083901.72850-1-roger.pau@citrix.com>

On 08.10.2024 10:39, Roger Pau Monne wrote:
> Some error paths in the MSR state loading logic don't contain error messages,
> which makes debugging them quite hard without adding extra patches to print the
> information.
> 
> Add two new log messages to the MSR state load path that print information
> about the entry that failed to load, for both PV and HVM.
> 
> While there also adjust XEN_DOMCTL_set_vcpu_msrs to return -ENXIO in case the
> MSR is unhandled or can't be loaded, so it matches the error code used by HVM
> MSR loading (and it's less ambiguous than -EINVAL).
> 
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>

Reviewed-by: Jan Beulich <jbeulich@suse.com>

> ---
> Changes since v1:
>  - Add messages to PV MSR loading.
>  - Return -ENXIO from PV loading path also.

I'm not fully convinced of the need to change the error code, but I also don't
mind it.

Jan



  reply	other threads:[~2024-10-08 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  8:39 [PATCH v2] x86/msr: add log messages to MSR state load error paths Roger Pau Monne
2024-10-08 12:41 ` Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-08  8:37 [PATCH] x86/domctl: fix maximum number of MSRs in XEN_DOMCTL_{get,set}_vcpu_msrs Roger Pau Monne
2024-10-08  8:37 ` [PATCH v2] x86/msr: add log messages to MSR state load error paths Roger Pau Monne
2024-10-08  9:00   ` Roger Pau Monné

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=24ac3cd7-5c49-49d2-9a74-9e8572c62dba@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=roger.pau@citrix.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.