From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>, <x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCHv1] x86: rtc_cmos platform device requires legacy irqs
Date: Fri, 4 Dec 2015 15:24:35 +0000 [thread overview]
Message-ID: <5661B033.10503@citrix.com> (raw)
In-Reply-To: <56619DCE.3050900@citrix.com>
On 04/12/15 14:06, David Vrabel wrote:
> On 03/12/15 10:43, David Vrabel wrote:
>> Adding the rtc platform device when there are no legacy irqs (no
>> legacy PIC) causes a conflict with other devices that end up using the
>> same irq number.
>
> An alternative is to remove the rtc_cmos platform device in Xen PV
> guests.
>
> Any preference on how this regression should be fixed?
>
> David
>
> 8<--------------------------
> x86: Xen PV guests don't have the rtc_cmos platform device
>
[...]
> --- a/arch/x86/kernel/rtc.c
> +++ b/arch/x86/kernel/rtc.c
> @@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void)
> }
> #endif
>
> + if (xen_pv_domain())
> + return -ENODEV;
> +
Note there's a missing include that breaks !XEN builds.
David
next prev parent reply other threads:[~2015-12-04 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 10:43 [PATCHv1] x86: rtc_cmos platform device requires legacy irqs David Vrabel
2015-12-03 11:23 ` [Xen-devel] " Vitaly Kuznetsov
2015-12-03 15:06 ` David Vrabel
2015-12-03 15:06 ` David Vrabel
2015-12-03 11:23 ` Vitaly Kuznetsov
2015-12-04 14:06 ` [Xen-devel] " David Vrabel
2015-12-04 15:24 ` David Vrabel [this message]
2015-12-04 15:35 ` Boris Ostrovsky
2015-12-04 15:35 ` [Xen-devel] " Boris Ostrovsky
2015-12-04 15:52 ` Vitaly Kuznetsov
2015-12-04 16:14 ` Boris Ostrovsky
2015-12-04 16:14 ` Boris Ostrovsky
2015-12-04 15:52 ` Vitaly Kuznetsov
2015-12-08 21:02 ` [Xen-devel] " Thomas Gleixner
2015-12-08 21:15 ` Boris Ostrovsky
2015-12-08 21:27 ` Thomas Gleixner
2015-12-08 21:27 ` Thomas Gleixner
2015-12-08 21:15 ` Boris Ostrovsky
2015-12-08 21:02 ` Thomas Gleixner
2015-12-04 15:24 ` David Vrabel
2015-12-04 14:06 ` David Vrabel
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=5661B033.10503@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--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.