On Tue, Dec 1, 2020 at 12:19 PM Scott Branden
wrote:
>
> Hi Masahiro,
>
> On 2020-12-01 4:25 a.m., Masahiro Yamada wrote:
> > On Sat, Nov 28, 2020 at 9:45 AM Scott Branden
> > wrote:
> >> From: Bruce Ashfield
> >>
> >> In some cross
On Tue, Oct 8, 2019 at 8:36 AM Oleg Nesterov wrote:
>
> On 10/08, Bruce Ashfield wrote:
> >
> > So I've been looking through the config delta's and late last night, I was
> > able to move the runtime back to a failed 4 minute state by adding the
> > CONFIG_PREEMPT se
On Mon, Oct 7, 2019 at 7:28 PM Roman Gushchin wrote:
>
> On Mon, Oct 07, 2019 at 04:11:07PM -0400, Bruce Ashfield wrote:
> > On Mon, Oct 7, 2019 at 8:54 AM Bruce Ashfield
> > wrote:
> > >
> > > On Thu, Oct 3, 2019 at 8:09 PM Roman Gushchin wrote:
> >
On Mon, Oct 7, 2019 at 8:54 AM Bruce Ashfield wrote:
>
> On Thu, Oct 3, 2019 at 8:09 PM Roman Gushchin wrote:
> >
> > On Wed, Oct 02, 2019 at 05:59:36PM -0400, Bruce Ashfield wrote:
> > > On Wed, Oct 2, 2019 at 2:19 PM Roman Gushchin wrote:
> > > >
>
On Thu, Oct 3, 2019 at 8:09 PM Roman Gushchin wrote:
>
> On Wed, Oct 02, 2019 at 05:59:36PM -0400, Bruce Ashfield wrote:
> > On Wed, Oct 2, 2019 at 2:19 PM Roman Gushchin wrote:
> > >
> > > On Wed, Oct 02, 2019 at 12:18:54AM -0400, Bruce Ashfield wrote:
> >
On Wed, Oct 2, 2019 at 2:19 PM Roman Gushchin wrote:
>
> On Wed, Oct 02, 2019 at 12:18:54AM -0400, Bruce Ashfield wrote:
> > On Tue, Oct 1, 2019 at 10:01 PM Roman Gushchin wrote:
> > >
> > > On Tue, Oct 01, 2019 at 12:14:18PM -0400, Bruce Ashfield wrote:
> >
On Tue, Oct 1, 2019 at 10:01 PM Roman Gushchin wrote:
>
> On Tue, Oct 01, 2019 at 12:14:18PM -0400, Bruce Ashfield wrote:
> > Hi all,
> >
>
> Hi Bruce!
>
> > The Yocto project has an upcoming release this fall, and I've been trying to
> > sort through som
Hi all,
The Yocto project has an upcoming release this fall, and I've been trying to
sort through some issues that are happening with kernel 5.2+ .. although
there is a specific yocto kernel, I'm testing and seeing this with
normal / vanilla
mainline kernels as well.
I'm running into an issue
The following commit has been merged into the x86/build branch of tip:
Commit-ID: 9e2276fa6eb39817dcc4cda415f0199fb7016b37
Gitweb:
https://git.kernel.org/tip/9e2276fa6eb39817dcc4cda415f0199fb7016b37
Author:Bruce Ashfield
AuthorDate:Thu, 26 Sep 2019 10:32:26 +01:00
On 2016-03-11 5:16 PM, Borislav Petkov wrote:
On Fri, Mar 11, 2016 at 08:18:23PM +0100, Paolo Bonzini wrote:
Somebody got it wrong 10-ish years ago, and nobody has ever checked since.
But, don't use qemu32 or qemu64. Use kvm32 and kvm64, or better
something like the host you run on ("-cpu
On 2016-03-11 5:16 PM, Borislav Petkov wrote:
On Fri, Mar 11, 2016 at 08:18:23PM +0100, Paolo Bonzini wrote:
Somebody got it wrong 10-ish years ago, and nobody has ever checked since.
But, don't use qemu32 or qemu64. Use kvm32 and kvm64, or better
something like the host you run on ("-cpu
On 10/28/2015 02:26 AM, Darren Hart wrote:
On Wed, Oct 28, 2015 at 09:42:06AM +0900, Olof Johansson wrote:
Kconfig knows how to handle CONFIG_FOO=n just fine, but it'll always
use "# CONFIG FOO is not set" in the resulting config. Mangle the input
accordingly so we don't report this as a
On 10/28/2015 01:02 AM, Darren Hart wrote:
On Wed, Oct 28, 2015 at 09:42:01AM +0900, Olof Johansson wrote:
Hi,
Somewhat wide distribution list here, since I've added everyone who's
touched the script, with the presumption that those have been the major
users of it. Please make sure none of
On 10/28/2015 02:26 AM, Darren Hart wrote:
On Wed, Oct 28, 2015 at 09:42:06AM +0900, Olof Johansson wrote:
Kconfig knows how to handle CONFIG_FOO=n just fine, but it'll always
use "# CONFIG FOO is not set" in the resulting config. Mangle the input
accordingly so we don't report this as a
On 10/28/2015 01:02 AM, Darren Hart wrote:
On Wed, Oct 28, 2015 at 09:42:01AM +0900, Olof Johansson wrote:
Hi,
Somewhat wide distribution list here, since I've added everyone who's
touched the script, with the presumption that those have been the major
users of it. Please make sure none of
On 8/23/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> By popular demand, here is release -v20 of the CFS scheduler. It is a
> full backport of the latest & greatest v2.6.23-rc3 CFS code to
> v2.6.22.5, v2.6.21.7 and v2.6.20.16. The patches can be downloaded from
> the usual place:
Ingo,
Great
On 8/23/07, Ingo Molnar [EMAIL PROTECTED] wrote:
By popular demand, here is release -v20 of the CFS scheduler. It is a
full backport of the latest greatest v2.6.23-rc3 CFS code to
v2.6.22.5, v2.6.21.7 and v2.6.20.16. The patches can be downloaded from
the usual place:
Ingo,
Great to see
H. Peter Anvin wrote:
Bruce Ashfield wrote:
These beasts are still alive and kicking. I boot a handful of
arm and ppc boards on a frequent basis that are zImage
only. The kicker is I don't have the bootloader source for
most of them, so changing to a different image format is
tough at best
H. Peter Anvin wrote:
Bruce Ashfield wrote:
These beasts are still alive and kicking. I boot a handful of
arm and ppc boards on a frequent basis that are zImage
only. The kicker is I don't have the bootloader source for
most of them, so changing to a different image format is
tough at best
On 6/11/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
I brought this up a few years ago, and had it shot down, because of a
few poorly substantiated claims of zImage-only machines; those claims
really need to be debugged since they might indicate A20-related failures.
These beasts are still
On 6/11/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
I brought this up a few years ago, and had it shot down, because of a
few poorly substantiated claims of zImage-only machines; those claims
really need to be debugged since they might indicate A20-related failures.
These beasts are still
On 12/6/06, Paul Sokolovsky <[EMAIL PROTECTED]> wrote:
Hello Lennert,
Wednesday, December 6, 2006, 3:08:13 AM, you wrote:
[]
> (These
> days I build all kernels in EABI mode with old-ABI compat.) I have
> not run into any code generation issues with this compiler yet.
I wonder, if
On 12/6/06, Paul Sokolovsky [EMAIL PROTECTED] wrote:
Hello Lennert,
Wednesday, December 6, 2006, 3:08:13 AM, you wrote:
[]
(These
days I build all kernels in EABI mode with old-ABI compat.) I have
not run into any code generation issues with this compiler yet.
I wonder, if OABI-compat
23 matches
Mail list logo
