xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 2/3] x86/viridian: Note that logging is under control of the guest
Date: Mon, 4 Aug 2014 14:38:18 +0100	[thread overview]
Message-ID: <53DF8CCA.1030702@citrix.com> (raw)
In-Reply-To: <1407157961-7239-3-git-send-email-paul.durrant@citrix.com>

On 04/08/14 14:12, Paul Durrant wrote:
> All viridian logging is actually in response to an action (MSR read/write,
> etc.) in the guest. As such XENLOG_G_ log levels should be used.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Keir Fraser <keir@xen.org>
> Cc: Jan Beulich <jbeulich@suse.com>

gdprintk() already makes them guest log levels, so this change is a
functional noop.

However, the __file__/__LINE__ references are quite useless in the
presented information, so can safely be dropped by switching to regular
printk().  It would also be nice to reduce the number of individual
lines requires.  dump_guest_os_id could easily be one or two lines
instead of 7.

~Andrew

> ---
>  xen/arch/x86/hvm/viridian.c |   26 +++++++++++++-------------
>  1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/xen/arch/x86/hvm/viridian.c b/xen/arch/x86/hvm/viridian.c
> index 31c9656..2d79403 100644
> --- a/xen/arch/x86/hvm/viridian.c
> +++ b/xen/arch/x86/hvm/viridian.c
> @@ -120,36 +120,36 @@ int cpuid_viridian_leaves(unsigned int leaf, unsigned int *eax,
>  
>  static void dump_guest_os_id(const struct domain *d)
>  {
> -    gdprintk(XENLOG_INFO, "GUEST_OS_ID:\n");
> -    gdprintk(XENLOG_INFO, "\tvendor: %x\n",
> +    gdprintk(XENLOG_G_INFO, "GUEST_OS_ID:\n");
> +    gdprintk(XENLOG_G_INFO, "\tvendor: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.vendor);
> -    gdprintk(XENLOG_INFO, "\tos: %x\n",
> +    gdprintk(XENLOG_G_INFO, "\tos: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.os);
> -    gdprintk(XENLOG_INFO, "\tmajor: %x\n",
> +    gdprintk(XENLOG_G_INFO, "\tmajor: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.major);
> -    gdprintk(XENLOG_INFO, "\tminor: %x\n",
> +    gdprintk(XENLOG_G_INFO, "\tminor: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.minor);
> -    gdprintk(XENLOG_INFO, "\tsp: %x\n",
> +    gdprintk(XENLOG_G_INFO, "\tsp: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.service_pack);
> -    gdprintk(XENLOG_INFO, "\tbuild: %x\n",
> +    gdprintk(XENLOG_G_INFO, "\tbuild: %x\n",
>              d->arch.hvm_domain.viridian.guest_os_id.fields.build_number);
>  }
>  
>  static void dump_hypercall(const struct domain *d)
>  {
> -    gdprintk(XENLOG_INFO, "HYPERCALL:\n");
> -    gdprintk(XENLOG_INFO, "\tenabled: %x\n",
> +    gdprintk(XENLOG_G_INFO, "HYPERCALL:\n");
> +    gdprintk(XENLOG_G_INFO, "\tenabled: %x\n",
>              d->arch.hvm_domain.viridian.hypercall_gpa.fields.enabled);
> -    gdprintk(XENLOG_INFO, "\tpfn: %lx\n",
> +    gdprintk(XENLOG_G_INFO, "\tpfn: %lx\n",
>              (unsigned long)d->arch.hvm_domain.viridian.hypercall_gpa.fields.pfn);
>  }
>  
>  static void dump_apic_assist(const struct vcpu *v)
>  {
> -    gdprintk(XENLOG_INFO, "APIC_ASSIST[%d]:\n", v->vcpu_id);
> -    gdprintk(XENLOG_INFO, "\tenabled: %x\n",
> +    gdprintk(XENLOG_G_INFO, "APIC_ASSIST[%d]:\n", v->vcpu_id);
> +    gdprintk(XENLOG_G_INFO, "\tenabled: %x\n",
>              v->arch.hvm_vcpu.viridian.apic_assist.fields.enabled);
> -    gdprintk(XENLOG_INFO, "\tpfn: %lx\n",
> +    gdprintk(XENLOG_G_INFO, "\tpfn: %lx\n",
>              (unsigned long)v->arch.hvm_vcpu.viridian.apic_assist.fields.pfn);
>  }
>  

  reply	other threads:[~2014-08-04 13:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 13:12 [PATCH v2 0/3] x86/viridian improvements Paul Durrant
2014-08-04 13:12 ` [PATCH v2 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask Paul Durrant
2014-08-04 13:31   ` Andrew Cooper
2014-08-04 13:50     ` Jan Beulich
2014-08-04 14:50       ` Andrew Cooper
2014-08-04 15:13         ` Jan Beulich
2014-08-04 17:19     ` Paul Durrant
2014-08-04 13:45   ` Jan Beulich
2014-08-04 13:12 ` [PATCH v2 2/3] x86/viridian: Note that logging is under control of the guest Paul Durrant
2014-08-04 13:38   ` Andrew Cooper [this message]
2014-08-04 13:45     ` Paul Durrant
2014-08-04 13:12 ` [PATCH v2 3/3] x86/viridian: Add partition time reference counter MSR support Paul Durrant
2014-08-04 14:01   ` Jan Beulich
2014-08-04 14:12     ` Paul Durrant
2014-08-04 14:47       ` Paul Durrant
2014-08-04 15:11         ` Paul Durrant
2014-08-04 15:15           ` Jan Beulich
2014-08-04 15:23             ` Paul Durrant

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=53DF8CCA.1030702@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=paul.durrant@citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).