From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH v2 6/6] x86/viridian: implement the crash MSRs
Date: Tue, 21 Mar 2017 15:50:09 +0000 [thread overview]
Message-ID: <bf89e3f020f54b5a88e2411d9049f8b7@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <58D157BA0200007800145CE3@prv-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 21 March 2017 15:42
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>; Wei Liu
> <wei.liu2@citrix.com>; Ian Jackson <Ian.Jackson@citrix.com>; xen-
> devel@lists.xenproject.org
> Subject: Re: [PATCH v2 6/6] x86/viridian: implement the crash MSRs
>
> >>> On 20.03.17 at 18:08, <paul.durrant@citrix.com> wrote:
> > @@ -619,6 +636,36 @@ int wrmsr_viridian_regs(uint32_t idx, uint64_t val)
> > update_reference_tsc(d, 1);
> > break;
> >
> > + case HV_X64_MSR_CRASH_P0:
> > + case HV_X64_MSR_CRASH_P1:
> > + case HV_X64_MSR_CRASH_P2:
> > + case HV_X64_MSR_CRASH_P3:
> > + case HV_X64_MSR_CRASH_P4:
> > + BUILD_BUG_ON(HV_X64_MSR_CRASH_P4 -
> HV_X64_MSR_CRASH_P0 >=
> > + ARRAY_SIZE(v->arch.hvm_vcpu.viridian.crash_param));
> > +
> > + idx -= HV_X64_MSR_CRASH_P0;
> > + v->arch.hvm_vcpu.viridian.crash_param[idx] = val;
> > + break;
> > +
> > + case HV_X64_MSR_CRASH_CTL:
> > + {
> > + HV_CRASH_CTL_REG_CONTENTS ctl;
> > +
> > + ctl.AsUINT64 = val;
> > +
> > + if ( !ctl.CrashNotify )
> > + break;
> > +
> > + gprintk(XENLOG_INFO, "VIRIDIAN CRASH: %lx %lx %lx %lx %lx\n",
> > + v->arch.hvm_vcpu.viridian.crash_param[0],
> > + v->arch.hvm_vcpu.viridian.crash_param[1],
> > + v->arch.hvm_vcpu.viridian.crash_param[2],
> > + v->arch.hvm_vcpu.viridian.crash_param[3],
> > + v->arch.hvm_vcpu.viridian.crash_param[4]);
>
> With default log level settings this message will go nowhere. If that's
> intended, I don't mind, but I think XENLOG_WARNING (or simply no
> log level) would be better here.
Oh, I thought INFO was on by default. Please change it to WARNING... it seems appropriate.
>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
>
> Let me know whether you want me to make the adjustment while
> committing.
>
Thanks but since I'm going to send a v3 anyway, I'll fix it.
Paul
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-21 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 17:08 [PATCH v2 0/6] viridian updates Paul Durrant
2017-03-20 17:08 ` [PATCH v2 1/6] x86/viridian: fix xen-hvmcrash when vp_assist page is present Paul Durrant
2017-03-21 15:26 ` Jan Beulich
2017-03-21 15:28 ` Paul Durrant
2017-03-20 17:08 ` [PATCH v2 2/6] x86/viridian: don't put Xen version information in CPUID leaf 2 Paul Durrant
2017-03-21 15:29 ` Jan Beulich
2017-03-21 15:45 ` Paul Durrant
2017-03-21 16:18 ` Jan Beulich
2017-03-20 17:08 ` [PATCH v2 3/6] x86/viridian: get rid of the magic numbers in CPUID leaves 1 and 2 Paul Durrant
2017-03-21 15:30 ` Jan Beulich
2017-03-20 17:08 ` [PATCH v2 4/6] x86/viridian: add warnings for unimplemented hypercalls and MSRs Paul Durrant
2017-03-21 15:32 ` Jan Beulich
2017-03-21 15:48 ` Paul Durrant
2017-03-20 17:08 ` [PATCH v2 5/6] x86/viridian: make the threshold for HvNotifyLongSpinWait tunable Paul Durrant
2017-03-21 15:35 ` Jan Beulich
2017-03-21 15:46 ` Paul Durrant
2017-03-20 17:08 ` [PATCH v2 6/6] x86/viridian: implement the crash MSRs Paul Durrant
2017-03-21 15:41 ` Jan Beulich
2017-03-21 15:50 ` Paul Durrant [this message]
2017-03-21 17:05 ` Wei Liu
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=bf89e3f020f54b5a88e2411d9049f8b7@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@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 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).