All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <hfp@posteo.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Steven Haigh <netwiz@crc.id.au>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Juergen Gross <JGross@suse.com>, Jan Beulich <JBeulich@suse.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	Roger Pau Monne <roger.pau@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>, Paul Durrant <paul@xen.org>
Subject: Re: [Xen-devel] Debugging Windows HVM crashes on Ryzen 3xxx series CPUs.
Date: Mon, 28 Oct 2019 12:03:29 +0100	[thread overview]
Message-ID: <cc16902a-bbad-00fe-291c-0b01c8231b60@posteo.de> (raw)
In-Reply-To: <f5bb6057-7d01-92ad-9ab5-45f4b5bf57a5@citrix.com>

Hello All,

> https://www.reddit.com/r/Amd/comments/ckr5f4/amd_ryzen_3000_series_linux_support_and/
> is concerning KVM, but it identified that the TOPOEXT feature was
> important to getting windows to boot.

I just tried qemu 3.1.1 with KVM (kernel 5.1.21) on a Ryzen 3700X and 
started qemu with "-cpu host,-topoext" and it still works perfectly. So 
it seems that TOPOEXT is not relevant.

Regards Andreas


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2019-10-28 11:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 11:57 [Xen-devel] Debugging Windows HVM crashes on Ryzen 3xxx series CPUs Steven Haigh
2019-10-24 14:45 ` Paul Durrant
2019-10-25  5:26   ` Steven Haigh
2019-10-25  7:00     ` Steven Haigh
2019-10-25  8:28       ` Jan Beulich
2019-10-25 10:10         ` Steven Haigh
2019-10-25 17:01 ` Andrew Cooper
2019-10-26  5:22   ` Jürgen Groß
2019-10-28  9:22     ` Jan Beulich
2019-10-28  9:21   ` Jan Beulich
2019-10-28 10:42     ` Paul Durrant
2019-10-28 11:18     ` Andrew Cooper
2019-10-28 11:46       ` Jan Beulich
2019-10-28 11:03   ` Andreas Kinzler [this message]

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=cc16902a-bbad-00fe-291c-0b01c8231b60@posteo.de \
    --to=hfp@posteo.de \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=netwiz@crc.id.au \
    --cc=paul@xen.org \
    --cc=roger.pau@citrix.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 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.