On 01/09/2013 11:59 AM, Rajagopal Venkat wrote:
> while reparenting a clock, NULL check is done for clock in
> consideration and its new parent. So re-check is not required.
> If done, else part becomes unreachable.
>
> Signed-off-by: Rajagopal Venkat
> ---
It is good to have revision history of
while reparenting a clock, NULL check is done for clock in
consideration and its new parent. So re-check is not required.
If done, else part becomes unreachable.
Signed-off-by: Rajagopal Venkat
---
drivers/clk/clk.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --g
On 9 January 2013 11:20, Tushar Behera wrote:
> On 01/08/2013 06:33 PM, Rajagopal Venkat wrote:
>> while reparenting a clock, NULL check is done for clock in
>> consideration and its new parent. So re-check is not required.
>> If done, else part becomes unreachable.
>>
>> Signed-off-by: Rajagopal
On 01/08/2013 06:33 PM, Rajagopal Venkat wrote:
> while reparenting a clock, NULL check is done for clock in
> consideration and its new parent. So re-check is not required.
> If done, else part becomes unreachable.
>
> Signed-off-by: Rajagopal Venkat
> ---
> drivers/clk/clk.c |5 +
> 1
Here comes the point of making both load balancing and wake up
balance(select_idle_sibling) co operative. How about we always schedule
the woken up task on the prev_cpu? This seems more sensible considering
load balancing considers blocked load as being a part of the load of cpu
On 2 January 2013 16:30, Zygmunt Krynicki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> W dniu 02.01.2013 16:58, Matthias Klose pisze:
>> A test rebuild of raring ringtail started in 2012 for the amd64,
>> i386 and armhf architectures is now finished for all components on
>> armhf.
On 8 January 2013 15:57, Richard Henderson wrote:
> On 01/08/2013 04:08 AM, Peter Maydell wrote:
>> The translator sources (as and when we implement a
>> TCG QEMU target for this) should live under the existing target-arm.
>
> Of this I'm not certain, given that A64 is different enough from A32
>
On 8 January 2013 07:06, Preeti U Murthy wrote:
> On 01/07/2013 09:18 PM, Vincent Guittot wrote:
>> On 2 January 2013 05:22, Preeti U Murthy wrote:
>>> Hi everyone,
>>> I have been looking at how different workloads react when the per entity
>>> load tracking metric is integrated into the load ba
We should be able to configure QEMU for cross compiling it for ARM64 host.
This patch only tries to make sure that the configure step falls through
and atleast QEMU cross-compilation starts.
The rationale behind cpu=aarch64 naming (as commented by Peter Maydell):
For the target architecture name
while reparenting a clock, NULL check is done for clock in
consideration and its new parent. So re-check is not required.
If done, else part becomes unreachable.
Signed-off-by: Rajagopal Venkat
---
drivers/clk/clk.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drive
On 8 January 2013 12:24, Anup Patel wrote:
> On 8 January 2013 17:38, Peter Maydell wrote:
>> Also, I suspect this isn't the only thing that will be required.
> Yes. This patch only tries to make sure that the configure step falls
> through and at-least QEMU cross-compilation starts.
It's gener
On 8 January 2013 17:38, Peter Maydell wrote:
> On 8 January 2013 11:05, Anup Patel wrote:
> > diff --git a/configure b/configure
> > index fe18ed2..0bfb8bb 100755
> > --- a/configure
> > +++ b/configure
> > @@ -366,6 +366,8 @@ elif check_define __s390__ ; then
> >fi
> > elif check_define _
On 8 January 2013 11:05, Anup Patel wrote:
> diff --git a/configure b/configure
> index fe18ed2..0bfb8bb 100755
> --- a/configure
> +++ b/configure
> @@ -366,6 +366,8 @@ elif check_define __s390__ ; then
>fi
> elif check_define __arm__ ; then
>cpu="arm"
> +elif check_define __aarch64__ ;
W dniu 08.01.2013 12:05, Anup Patel pisze:
> We should be able to cross compile QEMU for ARM64 host.
>
> This is required for trying out ARM 32-bit guest on ARM64 host using QEMU +
> KVM ARM64.
Which version you got built with this patch? 1.3.0 failed for me.
__
We should be able to cross compile QEMU for ARM64 host.
This is required for trying out ARM 32-bit guest on ARM64 host using QEMU + KVM
ARM64.
Signed-off-by: Anup Patel
---
configure |5 +
1 file changed, 5 insertions(+)
diff --git a/configure b/configure
index fe18ed2..0bfb8bb 100755
Hi Mike,
Thank you very much for such a clear and comprehensive explanation.
So when I put together the problem and the proposed solution pieces in the
current
scheduler scalability,the following was what I found:
1. select_idle_sibling() is needed as an agent to correctly find the right cpu
fo
16 matches
Mail list logo
