All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/3] n450: add 2.6.37 kernel recipe and SMP support
Date: Wed, 27 Apr 2011 15:19:43 -0700	[thread overview]
Message-ID: <4DB8967F.2020409@linux.intel.com> (raw)
In-Reply-To: <4DB875A5.30501@windriver.com>



On 04/27/2011 12:59 PM, Bruce Ashfield wrote:
> On 11-04-27 03:51 PM, Darren Hart wrote:
>> The atom-pc BSP which the n450 is based on was originally intended for single
>> CPU. The n450 is a single-core hyperthreaded CPU, so CONFIG_SMP and
>> CONFIG_SCHED_SMT are required to access the second hardware thread. These
>> patches add the newly created cfg/smp.scc config fragment to the recipe.
>>
>> The current n450 BSP uses linux-yocto-stable (2.6.34), which was an oversight.
>> These patches add support for the linux-yocto (2.6.37) recipe and separately
>> enable that as the default. I have tested the linux-yocto kernel and confirmed
>> it boots, has functional networking, and can suspend and resume.
>>
>> After some discussion with Tom, it seems that there is adequate testing planned
>> for the point release to allow for moving to the linux-yocto recipe. Note that
>> fixing bug 1010 makes significant changes to whichever kernel we choose
> 
> Was this supposed to read "does not make significant changes" ? Looks
> pretty minor to me (outside of jumping kernels :).

Actually no. There was some concern about jumping kernels and I just
want to point out that enabling SMP changes the way a number of things
work within the kernel, so some retesting might be necessary anyway. If
so, then the jump to 2.6.37 isn't as big of a deal.

> 
>> to use. Before I commit to meta-intel however, I would like the input of the QA
>> team.
>>
>> How much testing was planned for the n450 originally? How much additional
>> testing would be required if we make the new kernel the default?
> 
> For what its worth our other x86 testing should have largely covered
> this. If we can't count on the transitive value of our testing using
> the common fragments/drivers/arch, then we don't have much to count on.
> 
> I see little risk in this myself, and would support the default changing
> to linux-yocto in 1.0.1.

Excellent point Bruce!

> 
> Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> 
>>
>> Thanks,
>>
>> Darren Hart
>>
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-04-27 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 19:51 [PATCH 0/3] n450: add 2.6.37 kernel recipe and SMP support Darren Hart
2011-04-27 19:51 ` [PATCH 1/3] n450: enable SMP and SCHED_SMT Darren Hart
2011-04-27 19:52   ` [PATCH 2/3] n450: add linux_yocto (2.6.37) bbappend Darren Hart
2011-04-27 19:52   ` [PATCH 3/3] n450: use linux-yocto (2.6.37) by default Darren Hart
2011-04-27 19:59 ` [PATCH 0/3] n450: add 2.6.37 kernel recipe and SMP support Bruce Ashfield
2011-04-27 22:19   ` Darren Hart [this message]
2011-04-28  0:18     ` Bruce Ashfield

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=4DB8967F.2020409@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.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.