From: David Vrabel <david.vrabel@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Paul Durrant <paul.durrant@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 0/2] Viridian MSRs
Date: Wed, 16 Oct 2013 14:54:04 +0100 [thread overview]
Message-ID: <525E9A7C.1070703@citrix.com> (raw)
In-Reply-To: <525E965E.8000401@citrix.com>
On 16/10/13 14:36, Andrew Cooper wrote:
>
> I disagree. There is a perfectly good mechanism for advertising which
> viridian extensions are available, which was being blindly ignored by
> Linux (The specific bug was the HyperV drivers assuming a HyperV timer
> without checking that it was actually present, leading to an hang when
> waiting for a timer interrupt).
>
> This is a Linux bug; Xen should not be functionally crippled because a
> guest can't enumerate support correctly.
>
> And anyway - the entire set of viridian extensions is an off-by-default,
> opt-in configuration option in the first place. Anyone who decided to
> try Linux with viridan can turn it off if it doesn't work.
I think Jan is suggesting that you pre-emptively check that it doesn't
cause breakage in Linux. So that any Linux bugs (if there are any) can
be fixed sooner.
David
next prev parent reply other threads:[~2013-10-16 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 18:12 [PATCH 0/2] Viridian MSRs Andrew Cooper
2013-10-15 18:12 ` [PATCH 1/2] x86/viridian: Time Reference Count MSR Andrew Cooper
2013-11-05 15:27 ` Ian Campbell
2013-10-15 18:12 ` [PATCH 2/2] x86/viridian: TSC and APIC Frequency MSRs Andrew Cooper
2013-10-16 10:12 ` [PATCH 0/2] Viridian MSRs Jan Beulich
2013-10-16 11:05 ` Andrew Cooper
2013-10-16 11:21 ` Jan Beulich
2013-10-16 13:36 ` Andrew Cooper
2013-10-16 13:52 ` Paul Durrant
2013-10-16 13:54 ` David Vrabel [this message]
2013-11-05 15:15 ` Jan Beulich
2013-11-05 15:21 ` Paul Durrant
2013-11-05 15:28 ` Jan Beulich
2013-11-05 15:17 ` Jan Beulich
2013-11-05 15:22 ` Andrew Cooper
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=525E9A7C.1070703@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=paul.durrant@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.