On 12/09/2015 10:27 AM, Jan Beulich wrote:
On 09.12.15 at 16:15, wrote:
On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- a/arch/x86/kernel/rtc.c
+++ b/arch/x86/kernel/rtc.c
@@ -200,6 +200,9 @@ static __init int
>>> On 09.12.15 at 16:15, wrote:
> On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
>> On 2015-12-09 15:42, Jan Beulich wrote:
>> On 09.12.15 at 15:32, wrote:
--- a/arch/x86/kernel/rtc.c
+++ b/arch/x86/kernel/rtc.c
@@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void)
Sander Eikelenboom writes:
> On 2015-12-09 15:42, Jan Beulich wrote:
> On 09.12.15 at 15:32, wrote:
>>> --- 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 (paravirt_enabled())
>>> +
On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- 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 (paravirt_enabled())
+return
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- 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 (paravirt_enabled())
+ return -ENODEV;
What about Xen Dom0?
Jan
>>> On 09.12.15 at 15:32, wrote:
> --- 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 (paravirt_enabled())
> + return -ENODEV;
What about Xen Dom0?
Jan
--
To unsubscribe from this
Adding the rtc platform device in a Xen PV guests causes an IRQ
conflict because these guests do not have a legacy PIC.
In a single VCPU Xen PV guest we should have:
/proc/interrupts:
CPU0
0: 4934 xen-percpu-virq timer0
1: 0 xen-percpu-ipi spinlock0
On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- 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
Adding the rtc platform device in a Xen PV guests causes an IRQ
conflict because these guests do not have a legacy PIC.
In a single VCPU Xen PV guest we should have:
/proc/interrupts:
CPU0
0: 4934 xen-percpu-virq timer0
1: 0 xen-percpu-ipi spinlock0
>>> On 09.12.15 at 15:32, wrote:
> --- 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 (paravirt_enabled())
> + return -ENODEV;
What about Xen Dom0?
Jan
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- 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 (paravirt_enabled())
+ return -ENODEV;
Sander Eikelenboom writes:
> On 2015-12-09 15:42, Jan Beulich wrote:
> On 09.12.15 at 15:32, wrote:
>>> --- a/arch/x86/kernel/rtc.c
>>> +++ b/arch/x86/kernel/rtc.c
>>> @@ -200,6 +200,9 @@ static __init int add_rtc_cmos(void)
>>> }
>>>
>>> On 09.12.15 at 16:15, wrote:
> On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
>> On 2015-12-09 15:42, Jan Beulich wrote:
>> On 09.12.15 at 15:32, wrote:
--- a/arch/x86/kernel/rtc.c
+++ b/arch/x86/kernel/rtc.c
@@
On 12/09/2015 10:27 AM, Jan Beulich wrote:
On 09.12.15 at 16:15, wrote:
On 12/09/2015 10:00 AM, Sander Eikelenboom wrote:
On 2015-12-09 15:42, Jan Beulich wrote:
On 09.12.15 at 15:32, wrote:
--- a/arch/x86/kernel/rtc.c
+++
14 matches
Mail list logo