From: Andy Smith <andy@strugglers.net>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: 4.10.1 Xen crash and reboot
Date: Mon, 10 Dec 2018 16:44:23 +0000 [thread overview]
Message-ID: <20181210164423.GT3695@bitfolk.com> (raw)
In-Reply-To: <5C0E946E0200007800204CB8@prv1-mh.provo.novell.com>
Hi Jan,
On Mon, Dec 10, 2018 at 09:29:34AM -0700, Jan Beulich wrote:
> >>> On 10.12.18 at 16:58, <andy@strugglers.net> wrote:
> > Are there any other hypervisor command line options that would be
> > beneficial to set for next time?
>
> Well, just like for your report from a couple of weeks ago - if this is
> on PCID/INVPCID capable hardware, have you tried disabling use
> of PCID?
Aside from a quick test at Andrew's suggestion I have not, because I
thought there were negative repercussions of this, and up until this
point it seemed like problems were restricted to guests and could be
avoided by guest kernel upgrade.
The previous issue with the memory corruption in guests was avoided
by booting with pcid=0.
Does setting pcid=0 leave me increasingly vulnerable to Meltdown
and/or negatively impact performance?
Thanks,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-10 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 15:58 4.10.1 Xen crash and reboot Andy Smith
2018-12-10 16:29 ` Jan Beulich
2018-12-10 16:44 ` Andy Smith [this message]
2018-12-10 17:12 ` Jan Beulich
2018-12-21 18:55 ` Andy Smith
2019-01-01 19:46 ` Andy Smith
2019-01-04 10:16 ` Jan Beulich
2019-01-04 12:28 ` Andy Smith
2019-01-30 18:53 ` Andy Smith
-- strict thread matches above, loose matches on Subject: below --
2019-01-07 11:12 Patrick Beckmann
2019-02-11 10:41 ` Patrick Beckmann
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=20181210164423.GT3695@bitfolk.com \
--to=andy@strugglers.net \
--cc=JBeulich@suse.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.