On 11/01/2015 11:06 PM, Timur Tabi wrote:
> Fu Wei wrote:
>> In virtualization system, Linux kernel with KVM support as a
>> Hypervisor, and guest are using a one of SBSA watchdog.
>> WS0 is handled by guest OS, and WS1 will be handled by Hypervisor.
>
> I don't see how that would work, because
Hi Timur.
On 31 October 2015 at 04:37, Timur Tabi wrote:
> On 10/30/2015 02:05 PM, Mark Rutland wrote:
>>
>> I was only asking why the interrupt was optional, and it seems per the
>> spec it's expected to be handed to an agent at a higher exception level.
>>
>> That implies that the OS should
Fu Wei wrote:
In virtualization system, Linux kernel with KVM support as a
Hypervisor, and guest are using a one of SBSA watchdog.
WS0 is handled by guest OS, and WS1 will be handled by Hypervisor.
I don't see how that would work, because the host kernel cannot
reconfigure the behavior of
Hi Mark,
Great thanks for your feedback.
On 31 October 2015 at 03:05, Mark Rutland wrote:
> On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote:
>> On 10/30/2015 01:35 PM, Fu Wei wrote:
>> >>I think maybe Mark was asking why WS1 is optional, not the WS1
>> >My answer is for "why WS1 is
Hi Mark,
Great thanks for your feedback.
On 31 October 2015 at 03:05, Mark Rutland wrote:
> On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote:
>> On 10/30/2015 01:35 PM, Fu Wei wrote:
>> >>I think maybe Mark was asking why WS1 is optional, not the WS1
>> >My
Hi Timur.
On 31 October 2015 at 04:37, Timur Tabi wrote:
> On 10/30/2015 02:05 PM, Mark Rutland wrote:
>>
>> I was only asking why the interrupt was optional, and it seems per the
>> spec it's expected to be handed to an agent at a higher exception level.
>>
>> That implies
Fu Wei wrote:
In virtualization system, Linux kernel with KVM support as a
Hypervisor, and guest are using a one of SBSA watchdog.
WS0 is handled by guest OS, and WS1 will be handled by Hypervisor.
I don't see how that would work, because the host kernel cannot
reconfigure the behavior of
On 11/01/2015 11:06 PM, Timur Tabi wrote:
> Fu Wei wrote:
>> In virtualization system, Linux kernel with KVM support as a
>> Hypervisor, and guest are using a one of SBSA watchdog.
>> WS0 is handled by guest OS, and WS1 will be handled by Hypervisor.
>
> I don't see how that would work, because
On 10/30/2015 02:05 PM, Mark Rutland wrote:
I was only asking why the interrupt was optional, and it seems per the
spec it's expected to be handed to an agent at a higher exception level.
That implies that the OS should only care about WS0, assuming that I've
understood correctly.
Yes, this
On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote:
> On 10/30/2015 01:35 PM, Fu Wei wrote:
> >>I think maybe Mark was asking why WS1 is optional, not the WS1
> >My answer is for "why WS1 is optional"!
> >
> >>>interrupt. Maybe you can reword the documentation to make is clear
> >>>that
>
On 10/30/2015 01:35 PM, Fu Wei wrote:
I think maybe Mark was asking why WS1 is optional, not the WS1
My answer is for "why WS1 is optional"!
>interrupt. Maybe you can reword the documentation to make is clear
>that
I didn't say : "only the*interrupt* for WS1 is optional."
WS1 itself is
Hi Timur
On 31 October 2015 at 01:46, Timur Tabi wrote:
> On Tue, Oct 27, 2015 at 11:10 PM, Fu Wei wrote:
>>
>>> Why is WS1 optional?
>>
>> According to the description of WS1 in SBSA 2.3 (5.2 Watchdog Operation)
>> page 21
>> -
>> The signal is fed to a higher agent as an
On Tue, Oct 27, 2015 at 11:10 PM, Fu Wei wrote:
>
>> Why is WS1 optional?
>
> According to the description of WS1 in SBSA 2.3 (5.2 Watchdog Operation) page
> 21
> -
> The signal is fed to a higher agent as an interrupt or reset for it to
> take executive action.
>
On 10/30/2015 02:05 PM, Mark Rutland wrote:
I was only asking why the interrupt was optional, and it seems per the
spec it's expected to be handed to an agent at a higher exception level.
That implies that the OS should only care about WS0, assuming that I've
understood correctly.
Yes, this
On Fri, Oct 30, 2015 at 01:53:24PM -0500, Timur Tabi wrote:
> On 10/30/2015 01:35 PM, Fu Wei wrote:
> >>I think maybe Mark was asking why WS1 is optional, not the WS1
> >My answer is for "why WS1 is optional"!
> >
> >>>interrupt. Maybe you can reword the documentation to make is clear
> >>>that
>
On Tue, Oct 27, 2015 at 11:10 PM, Fu Wei wrote:
>
>> Why is WS1 optional?
>
> According to the description of WS1 in SBSA 2.3 (5.2 Watchdog Operation) page
> 21
> -
> The signal is fed to a higher agent as an interrupt or reset for it to
> take executive
On 10/30/2015 01:35 PM, Fu Wei wrote:
I think maybe Mark was asking why WS1 is optional, not the WS1
My answer is for "why WS1 is optional"!
>interrupt. Maybe you can reword the documentation to make is clear
>that
I didn't say : "only the*interrupt* for WS1 is optional."
WS1 itself is
Hi Timur
On 31 October 2015 at 01:46, Timur Tabi wrote:
> On Tue, Oct 27, 2015 at 11:10 PM, Fu Wei wrote:
>>
>>> Why is WS1 optional?
>>
>> According to the description of WS1 in SBSA 2.3 (5.2 Watchdog Operation)
>> page 21
>> -
>> The
Hi Mark
Thanks for your rapid feedback, I appreciate your help very much.
On 28 October 2015 at 00:22, Mark Rutland wrote:
> On Wed, Oct 28, 2015 at 12:06:35AM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
>>
On Wed, Oct 28, 2015 at 12:06:35AM +0800, fu@linaro.org wrote:
> From: Fu Wei
>
> The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
> introducing SBSA(Server Base System Architecture) Generic Watchdog
> device node info into FDT.
>
> Also add sbsa-gwdt introduction in
From: Fu Wei
The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
introducing SBSA(Server Base System Architecture) Generic Watchdog
device node info into FDT.
Also add sbsa-gwdt introduction in watchdog-parameters.txt
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
---
From: Fu Wei
The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
introducing SBSA(Server Base System Architecture) Generic Watchdog
device node info into FDT.
Also add sbsa-gwdt introduction in watchdog-parameters.txt
Acked-by: Arnd Bergmann
On Wed, Oct 28, 2015 at 12:06:35AM +0800, fu@linaro.org wrote:
> From: Fu Wei
>
> The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
> introducing SBSA(Server Base System Architecture) Generic Watchdog
> device node info into FDT.
>
> Also add
Hi Mark
Thanks for your rapid feedback, I appreciate your help very much.
On 28 October 2015 at 00:22, Mark Rutland wrote:
> On Wed, Oct 28, 2015 at 12:06:35AM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> The sbsa-gwdt.txt documentation in
24 matches
Mail list logo