Hi,
Currently, when one builds the linux kernel, it places .o files all
over the source code tree.
Is there a way to have the linux kernel build, but place all the .o
files into a separate build folder?
Similar to how cmake or ninja work when building C source code.
One possible advantage of
Hi,
The use case I am struggling with is the use of a Windows program
running in wine that is sending and receiving UDP packets.
This particular windows program uses SO_REUSEADDR socket option and
opens two sockets. Lets call the first one socket A, and the second
one Socket B.
The SO_REUSEADDR
On Tue, 20 Aug 2019 at 07:47, Daniel Drake wrote:
>
> Hi,
>
> And if there is a meaningful way to make the kernel behave better, that would
> obviously be of huge value too.
>
> Thanks
> Daniel
Hi,
Is there a way for an application to be told that there is a memory
pressure situation?
For
On Tue, 6 Aug 2019 at 02:09, Suren Baghdasaryan wrote:
>
> 80% of the last 10 seconds spent in full stall would definitely be a
> problem. If the system was already low on memory (which it probably
> is, or we would not be reclaiming so hard and registering such a big
> stall) then oom-killer
The real problem with any new system, is the hardware is designed and
then it is a challenge for the software developer to get the software
to boot on the new hardware.
The nirvana here would be to take the original hardware circuit
diagram, and process it to automatically create a config file.
The real problem with any new system, is the hardware is designed and
then it is a challenge for the software developer to get the software
to boot on the new hardware.
The nirvana here would be to take the original hardware circuit
diagram, and process it to automatically create a config file.
On 28 February 2013 00:02, Greg KH wrote:
> On Wed, Feb 27, 2013 at 11:27:30PM +0000, James Courtier-Dutton wrote:
>> On 26 February 2013 18:11, James Courtier-Dutton
>> wrote:
>> > On 26 February 2013 17:35, Greg KH wrote:
>> >> On Mon, Feb 25, 201
On 26 February 2013 18:11, James Courtier-Dutton wrote:
> On 26 February 2013 17:35, Greg KH wrote:
>> On Mon, Feb 25, 2013 at 07:45:45PM -0800, Greg KH wrote:
>>> On Mon, Feb 25, 2013 at 02:32:43PM -0800, Greg KH wrote:
>>> > On Mon, Feb 25, 2013 at 04:06
On 27 February 2013 11:27, Alexander Holler wrote:
> Am 27.02.2013 11:17, schrieb James Courtier-Dutton:
>
>
>> 3) Trust based on date. I trust everything from X that I put on my
>> system 2 weeks ago, but one week ago X got hacked, so don't trust
>> anything new from t
On 27 February 2013 09:35, ownssh wrote:
> David Howells redhat.com> writes:
>
>>
>>
>> Florian Weimer deneb.enyo.de> wrote:
>>
>> > Seriously, folks, can we go back one step and discuss what problem you
>> > are trying to solve? Is it about allowing third-party kernel modules
>> > in an
On 27 February 2013 09:35, ownssh own...@gmail.com wrote:
David Howells dhowells at redhat.com writes:
Florian Weimer fw at deneb.enyo.de wrote:
Seriously, folks, can we go back one step and discuss what problem you
are trying to solve? Is it about allowing third-party kernel modules
On 27 February 2013 11:27, Alexander Holler hol...@ahsoftware.de wrote:
Am 27.02.2013 11:17, schrieb James Courtier-Dutton:
3) Trust based on date. I trust everything from X that I put on my
system 2 weeks ago, but one week ago X got hacked, so don't trust
anything new from them until
On 26 February 2013 18:11, James Courtier-Dutton james.dut...@gmail.com wrote:
On 26 February 2013 17:35, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Feb 25, 2013 at 07:45:45PM -0800, Greg KH wrote:
On Mon, Feb 25, 2013 at 02:32:43PM -0800, Greg KH wrote:
On Mon, Feb 25, 2013 at 04:06
On 28 February 2013 00:02, Greg KH gre...@linuxfoundation.org wrote:
On Wed, Feb 27, 2013 at 11:27:30PM +, James Courtier-Dutton wrote:
On 26 February 2013 18:11, James Courtier-Dutton james.dut...@gmail.com
wrote:
On 26 February 2013 17:35, Greg KH gre...@linuxfoundation.org wrote
On 26 February 2013 17:35, Greg KH wrote:
> On Mon, Feb 25, 2013 at 07:45:45PM -0800, Greg KH wrote:
>> On Mon, Feb 25, 2013 at 02:32:43PM -0800, Greg KH wrote:
>> > On Mon, Feb 25, 2013 at 04:06:02PM +1000, Dave Airlie wrote:
>> > > On Mon, Feb 25, 2013 at 3:52 PM, Greg KH
>> > > wrote:
>> > >
On 26 February 2013 17:35, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Feb 25, 2013 at 07:45:45PM -0800, Greg KH wrote:
On Mon, Feb 25, 2013 at 02:32:43PM -0800, Greg KH wrote:
On Mon, Feb 25, 2013 at 04:06:02PM +1000, Dave Airlie wrote:
On Mon, Feb 25, 2013 at 3:52 PM, Greg KH
On 20 January 2013 13:27, Clemens Ladisch wrote:
> James Courtier-Dutton wrote:
>> I have been given a linux kernel sources tar file.
>> It contains a modified version of the linux kernel.
>> It is just source files, without any "git" history.
>&g
On 20 January 2013 13:27, Clemens Ladisch clem...@ladisch.de wrote:
James Courtier-Dutton wrote:
I have been given a linux kernel sources tar file.
It contains a modified version of the linux kernel.
It is just source files, without any git history.
What I would like to do is compare
Hi,
The basis for any secure boot is a way to detect that the system has
been tampered with or not. "Tamper Evidence".
There are two main vectors for a system to be tampered with. Someone
local to the machine and remote users who can access the machine
across a network interface. (this includes
Hi,
The basis for any secure boot is a way to detect that the system has
been tampered with or not. Tamper Evidence.
There are two main vectors for a system to be tampered with. Someone
local to the machine and remote users who can access the machine
across a network interface. (this includes the
On 31 July 2012 07:35, John Stultz wrote:
> So CAI Qian noticed recent boot trouble on a machine that had its CMOS
> clock configured for the year 8200.
> See: http://lkml.org/lkml/2012/7/29/188
>
> While running with a crazy CMOS clock isn't advised, and a simple
> "don't do that" might be
On 31 July 2012 07:35, John Stultz john.stu...@linaro.org wrote:
So CAI Qian noticed recent boot trouble on a machine that had its CMOS
clock configured for the year 8200.
See: http://lkml.org/lkml/2012/7/29/188
While running with a crazy CMOS clock isn't advised, and a simple
don't do that
J.A. Magallón wrote:
I need to get rid of -mregparm=3 on gcc's command line. It
is completely incompatible with the standard calling conventions
used in all our assembly-language files in our drivers. We make
very high-speed number-crunching drivers that munge high-speed
data into images. We
J.A. Magallón wrote:
I need to get rid of -mregparm=3 on gcc's command line. It
is completely incompatible with the standard calling conventions
used in all our assembly-language files in our drivers. We make
very high-speed number-crunching drivers that munge high-speed
data into images. We
DervishD wrote:
Bonjour Xavier :)
* Xavier Bestel <[EMAIL PROTECTED]> dixit:
Le samedi 10 novembre 2007 à 13:04 +0100, DervishD a écrit :
* Benny Halevy <[EMAIL PROTECTED]> dixit:
I would like to hear peoples opinion about the indentation convention
described below that
DervishD wrote:
Bonjour Xavier :)
* Xavier Bestel [EMAIL PROTECTED] dixit:
Le samedi 10 novembre 2007 à 13:04 +0100, DervishD a écrit :
* Benny Halevy [EMAIL PROTECTED] dixit:
I would like to hear peoples opinion about the indentation convention
described below that I
Daniel J Blueman wrote:
On 23 Aug, 07:00, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On Aug 23 2007 01:01, Richard Ballantyne wrote:
What file system that is already in the linux kernel do people recommend
I use for my laptop that now contains a solid state disk?
If I had to
Daniel J Blueman wrote:
On 23 Aug, 07:00, Jan Engelhardt [EMAIL PROTECTED] wrote:
On Aug 23 2007 01:01, Richard Ballantyne wrote:
What file system that is already in the linux kernel do people recommend
I use for my laptop that now contains a solid state disk?
If I had to
Chris Wright wrote:
> * James Courtier-Dutton ([EMAIL PROTECTED]) wrote:
>> If one could directly expose a device to the guest, this feature could
>> be extremely useful for me.
>> Is it possible? How would it manage to handle the DMA bus mastering?
>
> Yes it's poss
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>> This patch provides hypercalls for the i386 port I/O instructions,
>> which vastly helps guests which use native-style drivers. For certain
>> VMI workloads, this provides a performance boost of up to 30%. We
>> expect KVM and lguest to be
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
This patch provides hypercalls for the i386 port I/O instructions,
which vastly helps guests which use native-style drivers. For certain
VMI workloads, this provides a performance boost of up to 30%. We
expect KVM and lguest to be able to
Chris Wright wrote:
* James Courtier-Dutton ([EMAIL PROTECTED]) wrote:
If one could directly expose a device to the guest, this feature could
be extremely useful for me.
Is it possible? How would it manage to handle the DMA bus mastering?
Yes it's possible (Xen supports pci pass through
Chuck Ebbert wrote:
In-Reply-To: <[EMAIL PROTECTED]>
On Wed, 20 Dec 2006 14:21:03 +, Alistair John Strachan wrote:
Any ideas?
BUG: unable to handle kernel NULL pointer dereference at virtual address
0009
83 ca 10 or $0x10,%edx
3b
Chuck Ebbert wrote:
In-Reply-To: [EMAIL PROTECTED]
On Wed, 20 Dec 2006 14:21:03 +, Alistair John Strachan wrote:
Any ideas?
BUG: unable to handle kernel NULL pointer dereference at virtual address
0009
83 ca 10 or $0x10,%edx
3b
Linus Torvalds wrote:
On Wed, 13 Dec 2006, Greg KH wrote:
Numerous kernel developers feel that loading non-GPL drivers into the
kernel violates the license of the kernel and their copyright. Because
of this, a one year notice for everyone to address any non-GPL
compatible modules has been
Linus Torvalds wrote:
On Wed, 13 Dec 2006, Greg KH wrote:
Numerous kernel developers feel that loading non-GPL drivers into the
kernel violates the license of the kernel and their copyright. Because
of this, a one year notice for everyone to address any non-GPL
compatible modules has been
Ben Collins wrote:
Here's the list of proprietary drivers that are in Ubuntu's restricted
modules package:
madwifi (closed hal implementation, being replaced in openhal)
fritz
ati
nvidia
ltmodem (does that even still work?)
ipw3945d (not a kernel
Arjan van de Ven wrote:
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory
Duncan Sands wrote:
I'm really not convinced about the user-mode thing unless somebody can
show me a good reason for it. Not just some "wouldn't it be nice" kind of
thing. A real, honest-to-goodness reason that we actually _want_ to see
used.
Qemu? It would be nice if emulators could
Duncan Sands wrote:
I'm really not convinced about the user-mode thing unless somebody can
show me a good reason for it. Not just some wouldn't it be nice kind of
thing. A real, honest-to-goodness reason that we actually _want_ to see
used.
Qemu? It would be nice if emulators could directly
Arjan van de Ven wrote:
On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
Dear Linux developers,
I recently discovered that the Linux kernel on 32 bits x86 processors
reports the stack as being non-executable while it is actually
executable (because located in the same memory
Ben Collins wrote:
Here's the list of proprietary drivers that are in Ubuntu's restricted
modules package:
madwifi (closed hal implementation, being replaced in openhal)
fritz
ati
nvidia
ltmodem (does that even still work?)
ipw3945d (not a kernel
Alan wrote:
On Sat, 25 Nov 2006 00:54:53 -0500
Casey Dahlin <[EMAIL PROTECTED]> wrote:
Linus did say that he would do anything within reason to help desktop
linux forward, and frankly a big step forward would be to get error
messages to the user. What might be some safe options for overriding,
Alan wrote:
On Sat, 25 Nov 2006 00:54:53 -0500
Casey Dahlin [EMAIL PROTECTED] wrote:
Linus did say that he would do anything within reason to help desktop
linux forward, and frankly a big step forward would be to get error
messages to the user. What might be some safe options for overriding,
dragoran wrote:
Niko Nitsche wrote:
dragoran wrote:
Hello.
I am running FC4 and compiled a vanilla linux 2.6.13.
After booting the kernel I see an error messages that says that it was
unable to load snd-emu10k1 (see dmesg).
In dmesg I got this:
Sep 4 10:09:47 chello062178124144 kernel:
dragoran wrote:
Niko Nitsche wrote:
dragoran wrote:
Hello.
I am running FC4 and compiled a vanilla linux 2.6.13.
After booting the kernel I see an error messages that says that it was
unable to load snd-emu10k1 (see dmesg).
In dmesg I got this:
Sep 4 10:09:47 chello062178124144 kernel:
Greg KH wrote:
On Sat, Sep 03, 2005 at 12:17:57AM +0200, iSteve wrote:
Yes, I am rather interested -- could you please provide details about
this method?
For PCI drivers, just add the line:
.owner = THIS_MODULE,
to their struct pci_driver definition and you will get the symlink
Greg KH wrote:
On Sat, Sep 03, 2005 at 12:17:57AM +0200, iSteve wrote:
Yes, I am rather interested -- could you please provide details about
this method?
For PCI drivers, just add the line:
.owner = THIS_MODULE,
to their struct pci_driver definition and you will get the symlink
Mateusz Berezecki wrote:
Hello List Readers,
I would really appreciate any comment on the overall performance of task
switching with 25 000 threads running on the Linux system. I was asked to work
on some software which spawns 25 000 threads and I am really worried if
it will ever work on 2 CPU
Dominik Wezel wrote:
Problem
===
When turning on the laptop and during POST and GrUB loading, all ports
on the hub are enabled. During the USB initialization phase, when the
hub is detected, shortly all ports become disabled, then turn on again
(uhci_hcd detects the lo-speed ports).
Dominik Wezel wrote:
Problem
===
When turning on the laptop and during POST and GrUB loading, all ports
on the hub are enabled. During the USB initialization phase, when the
hub is detected, shortly all ports become disabled, then turn on again
(uhci_hcd detects the lo-speed ports).
Mateusz Berezecki wrote:
Hello List Readers,
I would really appreciate any comment on the overall performance of task
switching with 25 000 threads running on the Linux system. I was asked to work
on some software which spawns 25 000 threads and I am really worried if
it will ever work on 2 CPU
Takashi Iwai wrote:
At Sat, 20 Aug 2005 03:08:07 -0400,
Lee Revell wrote:
On Sat, 2005-08-20 at 08:48 +0200, Emmanuel Fleury wrote:
So, there is no project about this yet
No, not yet. The ALSA team has a contact at Creative, I guess the next
step is to ask them.
Maybe James knows at
Takashi Iwai wrote:
At Sat, 20 Aug 2005 03:08:07 -0400,
Lee Revell wrote:
On Sat, 2005-08-20 at 08:48 +0200, Emmanuel Fleury wrote:
So, there is no project about this yet
No, not yet. The ALSA team has a contact at Creative, I guess the next
step is to ask them.
Maybe James knows at
Adam Belay wrote:
On Thu, Jun 16, 2005 at 11:37:30PM +0100, James Courtier-Dutton wrote:
Hi,
I have tried conacting the mailing list for the PCMCIA subsystem in
Linux, but no-one seems to respond.
PCMCIA SUBSYSTEM
L: http://lists.infradead.org/mailman/listinfo/linux-pcmcia
S
Anyone wishing to help fix this, please see:
http://bugzilla.kernel.org/show_bug.cgi?id=5057
Takashi Iwai wrote:
At Tue, 09 Aug 2005 02:54:49 -0400,
Lee Revell wrote:
[added James to cc:]
On Mon, 2005-08-08 at 09:40 -0700, Fernando Lopez-Lezcano wrote:
On Sun, 2005-08-07 at 10:43, Andrew
Adam Belay wrote:
On Thu, Jun 16, 2005 at 11:37:30PM +0100, James Courtier-Dutton wrote:
Hi,
I have tried conacting the mailing list for the PCMCIA subsystem in
Linux, but no-one seems to respond.
PCMCIA SUBSYSTEM
L: http://lists.infradead.org/mailman/listinfo/linux-pcmcia
S
Anyone wishing to help fix this, please see:
http://bugzilla.kernel.org/show_bug.cgi?id=5057
Takashi Iwai wrote:
At Tue, 09 Aug 2005 02:54:49 -0400,
Lee Revell wrote:
[added James to cc:]
On Mon, 2005-08-08 at 09:40 -0700, Fernando Lopez-Lezcano wrote:
On Sun, 2005-08-07 at 10:43, Andrew
Thorsten Knabe wrote:
On Mon, 1 Aug 2005, Andrew Haninger wrote:
Thorsten: Please remember to include the list(s) when emailing those
links/numbers. I'd like to be able to watch it, too, and add any
information that I can, rather than entering a duplicate bug.
Hello.
I have taken a closer
Thorsten Knabe wrote:
On Mon, 1 Aug 2005, Andrew Haninger wrote:
Thorsten: Please remember to include the list(s) when emailing those
links/numbers. I'd like to be able to watch it, too, and add any
information that I can, rather than entering a duplicate bug.
Hello.
I have taken a closer
Adrian Bunk wrote:
This patch schedules obsolete OSS drivers (with ALSA drivers that
support the same hardware) for removal.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
I've Cc'ed the people listed in MAINTAINERS as being responsible for one
or more of these drivers, and I've also
Adrian Bunk wrote:
On Sun, Jul 31, 2005 at 12:04:59PM +0200, Felipe Alfaro Solana wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/
Why was the KERNEL_VERSION(a,b,c) macro removed from
include/linux/version.h? The removal breaks external drivers
Adrian Bunk wrote:
On Sun, Jul 31, 2005 at 12:04:59PM +0200, Felipe Alfaro Solana wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/
Why was the KERNEL_VERSION(a,b,c) macro removed from
include/linux/version.h? The removal breaks external drivers
Adrian Bunk wrote:
This patch schedules obsolete OSS drivers (with ALSA drivers that
support the same hardware) for removal.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
I've Cc'ed the people listed in MAINTAINERS as being responsible for one
or more of these drivers, and I've also
I have a problem with slab.c where it fails to boot the kernel.
The first call to kmem_cache_create():about line 1063: using the
INDEX_AC parameter succeeds and exits via the kcc:left_over route.
The second call to kmem_cache_create():about line 1069: using the
INDEX_L3 parameter fails and exits
I have a problem with slab.c where it fails to boot the kernel.
The first call to kmem_cache_create():about line 1063: using the
INDEX_AC parameter succeeds and exits via the kcc:left_over route.
The second call to kmem_cache_create():about line 1069: using the
INDEX_L3 parameter fails and exits
Chris Friesen wrote:
> Chris Wedgwood wrote:
>
>> On Mon, Apr 18, 2005 at 01:19:57PM +0900, Takashi Ikebe wrote:
>>
>>
>>> From our experience, sometimes patches became to dozens to hundreds
>>> at one patching, and in this case GDB based approach cause target
>>> process's availability descent.
Chris Friesen wrote:
Chris Wedgwood wrote:
On Mon, Apr 18, 2005 at 01:19:57PM +0900, Takashi Ikebe wrote:
From our experience, sometimes patches became to dozens to hundreds
at one patching, and in this case GDB based approach cause target
process's availability descent.
could you
Mark Fortescue wrote:
> Hi,
>
> I am writing a "Proprietry" driver module for a "Proprietry" PCI card and
> I have found that I can't use SYSFS on Linux-2.6.10.
>
> Why ?.
>
> I am not modifing the Kernel/SYSFS code so I should be able, to use all
> the SYSFS/internal kernel function calls
Mark Fortescue wrote:
Hi,
I am writing a Proprietry driver module for a Proprietry PCI card and
I have found that I can't use SYSFS on Linux-2.6.10.
Why ?.
I am not modifing the Kernel/SYSFS code so I should be able, to use all
the SYSFS/internal kernel function calls without
Pavel Machek wrote:
Hi!
Any thoughts on this one? We should come back from resume in 30-row mode,
shouldn't we?
Well, current state of video resume is "we are happy to see anything
at all".
HW info
Using vga=0xf07, default8x16 font, display has 30 lines
On powerup from S3 console has only 25
Pavel Machek wrote:
Hi!
Any thoughts on this one? We should come back from resume in 30-row mode,
shouldn't we?
Well, current state of video resume is "we are happy to see anything
at all".
HW info
Using vga=0xf07, default8x16 font, display has 30 lines
On powerup from S3 console has only 25
Pavel Machek wrote:
Hi!
Any thoughts on this one? We should come back from resume in 30-row mode,
shouldn't we?
Well, current state of video resume is we are happy to see anything
at all.
HW info
Using vga=0xf07, default8x16 font, display has 30 lines
On powerup from S3 console has only 25
Pavel Machek wrote:
Hi!
Any thoughts on this one? We should come back from resume in 30-row mode,
shouldn't we?
Well, current state of video resume is we are happy to see anything
at all.
HW info
Using vga=0xf07, default8x16 font, display has 30 lines
On powerup from S3 console has only 25
74 matches
Mail list logo
