* Andi Kleen <[EMAIL PROTECTED]> wrote:
> Ingo Molnar <[EMAIL PROTECTED]> writes:
> >
> > MAX_ARG_PAGES should work just fine. I think the 'getconf ARG_MAX'
> > output is hardcoded. (because the kernel does not provide the
> > information dynamically)
>
> Perhaps it would be a good idea to ma
Hi.
On Thu, 2005-09-01 at 16:24, Meelis Roos wrote:
> RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
> RD> I had to guess, I would bet the commit below is what broke you. I'm
> RD> including a patch that reverts it at the end of this email
>
> Nigel, have you tried re
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> It looks like Gigabit Ethernet is still having some problems. This is
> with the e1000 driver. If I remove all the qdisc_restart changes it
> starts to work the warning below goes away, but it has
> smp_processor_id warnings.
hmmm. The thing to wat
drivers/char/ipmi/ipmi_poweroff.c::proc_write_chassctrl()
a) does sscanf on userland pointer
b) does sscanf on array that is not guaranteed to have NUL in it
c) interprets input in incredibly cretinous way:
if strings doesn't start with a decimal number => as if it was "0".
Hi All,
An update of the uClinux (MMU-less) fixups against 2.6.13.
Strait forward merge of the current outstanding patchs from
2.6.12-uc0. A few updates and fixes, but not alot of change in
this one.
http://www.uclinux.org/pub/uClinux/uClinux-2.6.x/linux-2.6.13-uc0.patch.gz
Change log:
. im
* Tony Lindgren <[EMAIL PROTECTED]> [050831 16:21]:
> * Srivatsa Vaddagiri <[EMAIL PROTECTED]> [050831 14:20]:
> > On Wed, Aug 31, 2005 at 04:47:05PM +0530, Srivatsa Vaddagiri wrote:
> > > On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> > > > that sounds like a fundamental issue
Hi Srivatsa,
on LKML I did see your patch trying to increase the accuracy of tme pmtmr by
directly converting the PM-timer-ticks to jiffies. I think this is a good
idea but as you already recognized, it is not completely correct...
There are at least these issues:
1. "offset_last" corresponds
RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
RD> I had to guess, I would bet the commit below is what broke you. I'm
RD> including a patch that reverts it at the end of this email
Nigel, have you tried reverting the patch Roland pointed out? It
probably helps you.
I
From: Ed L Cashin <[EMAIL PROTECTED]>
Date: Wed, 31 Aug 2005 11:50:55 -0400
> Jim MacBaine <[EMAIL PROTECTED]> writes:
>
> > Aug 31 15:18:49 sunny kernel: devfs_mk_dir: invalid argument.<6>
> > etherd/e0.0: unknown partition table
> > Aug 31 15:18:49 sunny kernel: aoe: 0011d8xx e0.0 v4000 has
Not tested, but it's rather obvious.
--
vda
--- linux-2.6.12.src/drivers/i2c/chips/via686a.c.orig Sun Jun 19 16:10:10 2005
+++ linux-2.6.12.src/drivers/i2c/chips/via686a.c Tue Aug 30 00:21:39 2005
@@ -205,7 +205,7 @@ static inline u8 FAN_TO_REG(long rpm, in
but the function is very linear in the
On Wed, Aug 31, 2005 at 08:11:12PM -0700, Ian Romanick wrote:
| Allen Akin wrote:
| > Jon's right about this: If you can accelerate a given simple function
| > (blending, say) for a 2D driver, you can accelerate that same function
| > in a Mesa driver for a comparable amount of effort, and deliver
On 9/1/05, Ian Romanick <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Allen Akin wrote:
> > On Wed, Aug 31, 2005 at 02:06:54PM -0700, Keith Packard wrote:
> > |
> > | ...So far, 3D driver work has proceeded almost entirely on the
> > | newest documented h
On Wednesday 31 August 2005 16:43, Greg KH wrote:
> On Thu, Aug 18, 2005 at 02:50:19PM -0500, Dmitry Torokhov wrote:
> > On 8/18/05, Greg KH <[EMAIL PROTECTED]> wrote:
> > > @@ -500,9 +519,13 @@ int class_device_add(struct class_device
> > >}
> > >
> > >class_device_add_attrs(class
OGAWA Hirofumi wrote:
"Machida, Hiroyuki" <[EMAIL PROTECTED]> writes:
Right, it looks like TLB, which holds cache "Physical addres"
correponding to "Logical address". In this case, PID and file name
to be looked up, perform role of "Logical address".
But, there is the big difference between
This patch implements IOCHK interfaces that enable PCI drivers to
detect error and make their error handling easier.
Please refer archives if you need, e.g. http://lwn.net/Articles/139240/
Thanks,
H.Seto
Signed-off-by: Hidetoshi Seto <[EMAIL PROTECTED]>
---
drivers/pci/pci.c |2
This patch implements ia64-specific IOCHK interfaces that enable
PCI drivers to detect error and make their error handling easier.
Please refer archives if you need, e.g. http://lwn.net/Articles/139240/
Thanks,
H.Seto
Signed-off-by: Hidetoshi Seto <[EMAIL PROTECTED]>
---
arch/ia64/Kconfig
On Thu, 1 Sep 2005 02:58 am, Srivatsa Vaddagiri wrote:
> Following patches related to dynamic tick are posted in separate mails,
> for convenience of review. The first patch probably applies w/o dynamic
> tick consideration also.
>
> Patch 1/3 -> Fixup lost tick calculation in timer_pm.c
> Patch 2
This patch makes UP and SMP do the same thing as far as module per-cpu
data go.
Unfortunately it affects core code.
To repeat the problem:
IA64 keeps per-cpu data in a small data area that is referenced by a
22-bit offset, for both UP and SMP cases. If a module defines
per-cpu data, it t
On Wed, 2005-08-31 at 18:58 -0700, Allen Akin wrote:
> On Wed, Aug 31, 2005 at 02:06:54PM -0700, Keith Packard wrote:
> | On Wed, 2005-08-31 at 13:06 -0700, Allen Akin wrote:
> | > ...
> |
> | Right, the goal is to have only one driver for the hardware, whether an
> | X server for simple 2D only e
Below find an updated hdaps driver.
Various bug fixes, clean ups, additions to the DMI whitelist, and a new
automatic inversion detector (some ThinkPads have the axises negated).
Andrew, since a new 2.6-mm has yet to come out, feel free to replace the
original patch with this one.
Thanks,
On Tue, 30 Aug 2005 19:07:55 +0800 jeff shia wrote:
> but It seems that I can not open sr0 with openflags O_RDWR,why?
> open("/dev/sr0",O_RDWR);
>
> It says:sr0 is a read only file sytem.
> why?
What media did you have in the drive?
For me, with a CD-ROM, I get the same that you reported,
but w
Hi.
On Thu, 2005-09-01 at 13:29, Kyle Moffett wrote:
> The 4020 and 0402 look oddly symmetrical to me, but that could just
> be my imagination.
All I saw in it was byte n+1 = byte n >> 1. Can't see any use to that
either, though. Maybe it's just there to torment reverse engineerers, or
trap memor
Hi:
Thanks to Yingchao Zhou and Gaurav Dhiman first, for your answers.
I get it now! but it look we must update knownledge about this.
I read copy_thread() in arch/i386/kernel/process.c, the code piece of
this function are:
/* childregs = ((struct pt_regs *) (THREAD_SIZE + (unsigned long)
p->t
On Aug 31, 2005, at 16:32:11, Vojtech Pavlik wrote:
On Wed, Aug 31, 2005 at 08:53:19PM +0100, Russell King wrote:
On Wed, Aug 31, 2005 at 12:55:12PM -0400, Mark Lord wrote:
I'll try loading the works into another ARM
system I have here, and see (1) if it runs as-is,
and (2) what the disassemb
2005/9/1, jmerkey <[EMAIL PROTECTED]>:
> Bernd,
>
> It might be helpful for someone to look at these sections of code I had
> to patch in 2.6.9.
> I discovered a case where the kernel scheduler will pass NULL for the
> array argument
> when I started hitting the extreme upper range > 200MB/S combin
Em Qua, 2005-08-31 às 13:56 -0700, Greg KH escreveu:
> On Wed, Aug 31, 2005 at 12:34:58PM -0300, Mauro Carvalho Chehab wrote:
> > Em Ter, 2005-08-30 ?s 23:20 +0200, Jean Delvare escreveu:
> > > Hi Mauro,
> > >
> > > > (...) it would be nice not to have a different I2C
> > > > API for every single
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen Akin wrote:
> On Wed, Aug 31, 2005 at 02:06:54PM -0700, Keith Packard wrote:
> |
> | ...So far, 3D driver work has proceeded almost entirely on the
> | newest documented hardware that people could get. Going back and
> | spending months
When building with CONFIG_PHYLIB=y on Itanium, I see:
`mdio_bus_exit' referenced in section `.init.text' of
drivers/built-in.o: defined in discarded section `.exit.text' of
drivers/built-in.o
I believe that mdio_bus_exit should not be declared __exit, because it
is referencesd from __init secti
David Brownell wrote:
Interesting. I start to like this shape better; it moves more of the
logic to operating point code, where it can make the sysfs interface
talk in terms of meaningful abstractions, not cryptic numeric offsets.
But it was odd to see the first patch be platform-specific suppor
Bernd,
It might be helpful for someone to look at these sections of code I had
to patch in 2.6.9.
I discovered a case where the kernel scheduler will pass NULL for the
array argument
when I started hitting the extreme upper range > 200MB/S combined disk
and lan
throughput. This was running wi
applied patches 1-18
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
> Linus Torvalds wrote:
> > There it is.
> >
> > The most painful part of 2.6.13 is likely to be the fact that we made x86
> > use the generic PCI bus setup code for assigning unassigned resources.
> > That uncovered rather a lot o
Bernd Eckenfels wrote:
In article <[EMAIL PROTECTED]> you wrote:
I mean, nvidia people also use propietary code in the kernel (probably
violating the GPL anyway) and don't do such things.
The Linux kernel allows binary drivers, you just have to live with a limited
number of exported s
On Wed, Aug 31, 2005 at 02:06:54PM -0700, Keith Packard wrote:
| On Wed, 2005-08-31 at 13:06 -0700, Allen Akin wrote:
| > ...
|
| Right, the goal is to have only one driver for the hardware, whether an
| X server for simple 2D only environments or a GL driver for 2D/3D
| environments. ...
I count
The iseries_veth driver can attach to multiple vlans, which correspond to
multiple net devices. However there is only 1 connection between each LPAR,
so the connection structure may be shared by multiple net devices.
This makes module removal messy, because we can't deallocate the connections
unti
There's a number of problems with the way iseries_veth counts TX errors.
Firstly it counts conditions which aren't really errors as TX errors. This
includes if we don't have a connection struct for the other LPAR, or if the
other LPAR is currently down (or just doesn't want to talk to us). Neither
Currently the iseries_veth driver contravenes the specification in
Documentation/networking/driver.txt, in that if packets are not acked by
the other LPAR they will sit around forever.
This patch adds a per-connection timer which fires if we've had no acks for
five seconds. This is superior to the
To aid in field debugging, add sysfs support for iseries_veth's connection
structures. At the moment this is all read-only, however we could think about
adding write support for some attributes in future.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/iseries_veth.c | 94 +
The iseries_veth driver unconditionally calls dma_unmap_single() even
when the corresponding dma_map_single() may have failed.
Rework the code a bit to keep the return value from dma_unmap_single()
around, and then check if it's a dma_mapping_error() before we do
the dma_unmap_single().
Signed-of
The iseries_veth driver often has multiple netdevices sending packets over
a single connection to another LPAR. If the bandwidth to the other LPAR is
exceeded, all the netdevices must have their queues stopped.
The current code achieves this by queueing one incoming skb on the
per-netdevice port s
This patch makes veth_init_connection() and veth_destroy_connection()
symmetrical in that they allocate/deallocate the same data.
Currently if there's an error while initialising connections (ie. ENOMEM)
we call veth_module_cleanup(), however this will oops because we call
driver_unregister() befo
The iseries_veth driver uses the generic TX timeout watchdog, however a better
solution is in the works, so remove this code.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/iseries_veth.c | 48 -
1 files changed, 48 deletions(-)
iseries_veth.h is only used by iseries_veth.c, so merge the former into
the latter.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/iseries_veth.h | 46 -
drivers/net/iseries_veth.c | 42 +++--
The iseries_veth driver has a timer which we use to send acks. When the
connection is reset or stopped we need to delete the timer.
Currently we only call del_timer() when resetting a connection, which means
the timer might run again while the connection is being re-setup. As it turns
out that's o
The iseries_veth driver uses atomic ops to manipulate the in_use field of
one of its per-connection structures. However all references to the
flag occur while the connection's lock is held, so the atomic ops aren't
necessary.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/is
Currently the iseries_veth driver prints the file name and line number in its
error messages. This isn't very useful for most users, so just print
"iseries_veth: message" instead.
- convert uses of veth_printk() to veth_debug()/veth_error()/veth_info()
- make terminology consistent, ie. always r
The iseries_veth driver contains a state machine which is used to manage
how connections are setup and neogotiated between LPARs.
If one side of a connection resets for some reason, the two LPARs can get
stuck in a race to re-setup the connection. This can lead to the connection
being declared dea
The iseries_veth driver keeps a stack of messages for each connection
and a lock to protect the stack. However there is also a per-connection lock
which makes the message stack lock redundant.
Remove the message stack lock and document the fact that callers of the
stack-manipulation functions must
Having merged iseries_veth.h, let's remove some of the studly caps that came
with it.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/iseries_veth.c | 74 ++---
1 files changed, 37 insertions(+), 37 deletions(-)
Index: veth-dev2/driv
Due to a logic bug, once promiscuous mode is enabled in the iseries_veth
driver it is never disabled.
The driver keeps two flags, promiscuous and all_mcast which have exactly the
same effect. This is because we only ever receive packets destined for us,
or multicast packets. So consolidate them in
Also to aid debugging, add sysfs support for iseries_veth's port structures.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
---
drivers/net/iseries_veth.c | 67 +
1 files changed, 67 insertions(+)
Index: veth-dev2/drivers/net/iseries_veth.c
===
Hi,
This is a series of patches for the iseries_veth driver. Most of these are
pretty much unchanged since I posted them earlier:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0506.3/1837.html
I've added patches to add sysfs support, and do some further code cleanups.
Please merge if they look o
The iseries_veth driver tells sysfs that it's called 'iseries_veth', but if
you ask it via ethtool it thinks it's called 'veth'. I think this comes from
2.4 when the driver was called 'veth', but it's definitely called
'iseries_veth' now, so fix it.
To make sure we don't do it again define DRV_NAM
> "Ian" == Ian Romanick <[EMAIL PROTECTED]> writes:
Ian> I'd really like to see a list of areas where OpenGL
Ian> isn't up to snuff for 2D operations.
Is that OpenVR spec from Khronos a reasonable baseline
for such a list?
-JimC
--
James H. Cloos, Jr. <[EMAIL PROTECTED]>
-
To unsubscribe f
In article <[EMAIL PROTECTED]> you wrote:
> I disagree with the language and the characterization that our
> proprietary user application code is "tainted."
The kernel is tainted if you install non-open source modules. You are not
allowed to circumvent this mechanism if you want to ship binary on
In article <[EMAIL PROTECTED]> you wrote:
> I mean, nvidia people also use propietary code in the kernel (probably
> violating the GPL anyway) and don't do such things.
The Linux kernel allows binary drivers, you just have to live with a limited
number of exported symbols and that the kernel is ta
On Wed, Aug 31, 2005 at 12:34:58PM -0300, Mauro Carvalho Chehab wrote:
> Em Ter, 2005-08-30 ?s 23:20 +0200, Jean Delvare escreveu:
> > Hi Mauro,
> >
> > > (...) it would be nice not to have a different I2C
> > > API for every single 2.6 version :-) It would be nice to change I2C
> > > API once and
On Thu, Aug 18, 2005 at 02:50:19PM -0500, Dmitry Torokhov wrote:
> On 8/18/05, Greg KH <[EMAIL PROTECTED]> wrote:
> > @@ -500,9 +519,13 @@ int class_device_add(struct class_device
> >}
> >
> >class_device_add_attrs(class_dev);
> > - if (class_dev->dev)
> > + if (class_d
On Thu, Aug 18, 2005 at 01:35:46PM +0800, Shaohua Li wrote:
> Hi,
> It appears pci_enable_msi doesn't reconfigure msi registers if it
> successfully look up a msi for a device. It assumes the data and address
> registers unchanged after calling pci_disable_msi. But this isn't always
> true, such as
On Thu, 2005-09-01 at 01:50 +0200, Roman Zippel wrote:
> What "more versions" are you talking about? When you convert a user time
> to kernel time you can automatically validate it and later you can use
> standard kernel APIs, so you don't have to add even more API bloat.
What's kernel time? Ar
Diego Calleja wrote:
El Wed, 31 Aug 2005 14:27:47 -0600,
"Jeff V. Merkey" <[EMAIL PROTECTED]> escribió:
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the he
>From: Roman Zippel [mailto:[EMAIL PROTECTED]
>On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
>
>> I cannot produce (top of my head) any other POSIX API calls that
>> allow you to specify another clock source, but they are there,
>> somewhere. If I am to introduce a new API, I better make it
>>
[PATCH] v9fs: cleanup fd transport
Signed-off-by: Latchesar Ionkov <[EMAIL PROTECTED]>
Signed-off-by: Eric Van Hensbegren <[EMAIL PROTECTED]>
---
commit a1949213f1723a7b8bba8edfa118985460d31604
tree 40224cafbfb68543c60a8e0f04ae669cba2cedf7
parent 3f92b2539fe581ee9011d687fbd43cebb641465e
author Er
[PATCH] v9fs: Support to force umount
Support for force umount
Signed-off-by: Latchesar Ionkov <[EMAIL PROTECTED]>
Signed-off-by: Eric Van Hensbergen <[EMAIL PROTECTED]>
---
commit 3f92b2539fe581ee9011d687fbd43cebb641465e
tree cd34696129c3b636b85578f659f260100196dee1
parent 83f1fe3d2adc3746d719e
Hi,
On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
> I cannot produce (top of my head) any other POSIX API calls that
> allow you to specify another clock source, but they are there,
> somewhere. If I am to introduce a new API, I better make it
> flexible enough so that other subsystems can u
Ingo Molnar <[EMAIL PROTECTED]> writes:
>
> MAX_ARG_PAGES should work just fine. I think the 'getconf ARG_MAX'
> output is hardcoded. (because the kernel does not provide the
> information dynamically)
Perhaps it would be a good idea to make it a sysctl. Is there
any reason it should be hardco
Followup to: <[EMAIL PROTECTED]>
By author:=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> This patch adds support for UTF-8 signatures (aka BOM, byte order
> mark) to binfmt_script. Files that start with EF BF FF # ! are now
> recognized as sc
>From: Roman Zippel [mailto:[EMAIL PROTECTED]
>On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
>
>> Usefulness: (see the rationale in the patch), but in a nutshell;
>> most POSIX timeout specs have to be absolute in CLOCK_REALTIME
>> (eg: pthread_mutex_timed_lock()). Current kernel needs the time
El Wed, 31 Aug 2005 14:27:47 -0600,
"Jeff V. Merkey" <[EMAIL PROTECTED]> escribió:
>
> NOTE! This copyright does *not* cover user programs that use kernel
> services by normal system calls - this is merely considered normal use
> of the kernel, and does *not* fall under the heading of "derived
>From: Christopher Friesen [mailto:[EMAIL PROTECTED]
>Perez-Gonzalez, Inaky wrote:
>
>>>I can get the first sleep. Suppose I oversleep by X nanoseconds. I
>>>wake, and get an opaque timeout back. How do I ask for the new wake
>>>time to be "endtime + INTERVAL"?
>>
>>
>> endtime.ts += INTERVAL
>>
Perez-Gonzalez, Inaky wrote:
I can get the first sleep. Suppose I oversleep by X nanoseconds. I
wake, and get an opaque timeout back. How do I ask for the new wake
time to be "endtime + INTERVAL"?
endtime.ts += INTERVAL
[we all know opaque is relative too]
Heh. Okay, then what are the r
On Thu, Sep 01, 2005 at 08:47:36AM +1000, Con Kolivas wrote:
> On Thu, 1 Sep 2005 06:07 am, daniel mclellan wrote:
> > Yes.
> >
> >
> > Linux yavanna 2.6.13-ckx1 #1 Tue Aug 30 04:03:25 EST 2005 x86_64 AMD
> > Athlon(tm) 64 FX-53 Processor AuthenticAMD GNU/Linux
> >
> > On Wednesday 31 August 2005 1
Hi,
On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
> >Why is that needed in a _general_ timeout API? What exactly makes it so
> >useful for everyone and not just more complex for everyone?
>
> Because if a system call gets a timeout specification it needs to
> verify its correctness first. In
On Wed, 2005-08-31 at 15:36 -0700, Zachary Amsden wrote:
> >I feel lost ticks can be based on cycles difference directly
> >rather than being based on microseconds that has elapsed.
> >
> >Following patch is in that direction.
> >
> >With this patch, time had kept up really well on one particular
On Thu, 1 Sep 2005 06:07 am, daniel mclellan wrote:
> Yes.
>
>
> Linux yavanna 2.6.13-ckx1 #1 Tue Aug 30 04:03:25 EST 2005 x86_64 AMD
> Athlon(tm) 64 FX-53 Processor AuthenticAMD GNU/Linux
>
> On Wednesday 31 August 2005 14:49, Rodney Gordon II wrote:
> > On Mon, Aug 29, 2005 at 05:03:24PM +1000, C
Srivatsa Vaddagiri wrote:
On Wed, Aug 31, 2005 at 10:28:43PM +0530, Srivatsa Vaddagiri wrote:
Following patches related to dynamic tick are posted in separate mails,
for convenience of review. The first patch probably applies w/o dynamic
tick consideration also.
Patch 1/3 -> Fixup lost tic
From: Jim Keniston <[EMAIL PROTECTED]>
Date: 31 Aug 2005 14:53:37 -0700
> This bug doesn't exist on ppc64 and ia64, where a breakpoint
> instruction leaves the IP pointing to the beginning of the instruction.
> I don't know about sparc64. (Dave, could you please advise?)
On sparc64 instructions
Jesper Juhl wrote:
Well, it wouldn't have to be initrd specifically. Generally what's
needed is *some* way to tell the kernel "please read more options from
location ". The interresting bit is what 's supposed to be.
This is what initramfs (as opposed to initrd) does quite well.
-hpa
>From: Christopher Friesen [mailto:[EMAIL PROTECTED]
>Joe Korty wrote:
>
>> The returned timeout struct has a bit used to mark the value as
absolute. Thus
>> the caller treats the returned timeout as a opaque cookie that can be
>> reapplied to the next (or more likely, the to-be restarted) timeout
On Wed, Aug 31, 2005 at 03:19:37PM -0600, Bjorn Helgaas wrote:
> On Wednesday 31 August 2005 2:10 pm, Tom Rini wrote:
> > On Wed, Aug 31, 2005 at 01:38:52PM -0600, Bjorn Helgaas wrote:
> > > On Monday 29 August 2005 10:09 am, Tom Rini wrote:
> > I've tried intentionally to not mention 'ttyS' anywhe
On Thu, Sep 01, 2005 at 12:12:00AM +0200, Jesper Juhl wrote:
> b) add a new boot option telling the kernel the name of some file in
> initrd or similar from which to load additional options.
a file in initrd isn't a good choice; as the initrd is generally a fix
image
the point is some bootloader
Chris Wedgwood wrote:
On Wed, Aug 31, 2005 at 03:01:57PM -0700, H. Peter Anvin wrote:
Maybe not. Another option would simply be to bump it up
significantly (2x isn't really that much.) 4096, maybe.
I wonder if we're not at the point where we need something different
to what we have now. Th
Chris Wedgwood wrote:
On Thu, Sep 01, 2005 at 12:12:00AM +0200, Jesper Juhl wrote:
b) add a new boot option telling the kernel the name of some file in
initrd or similar from which to load additional options.
a file in initrd isn't a good choice; as the initrd is generally a fix
image
the po
>From: Roman Zippel [mailto:[EMAIL PROTECTED]
>On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
>
>> +flags = tp->clock_id & TIMEOUT_FLAGS_MASK;
>> +clock_id = tp->clock_id & TIMEOUT_CLOCK_MASK;
>> +
>> +result = -EINVAL;
>> +if (flags & ~TIMEOUT_RELATIVE)
>> +goto out;
>>
On 9/1/05, Chris Wedgwood <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 01, 2005 at 12:12:00AM +0200, Jesper Juhl wrote:
>
> > b) add a new boot option telling the kernel the name of some file in
> > initrd or similar from which to load additional options.
>
> a file in initrd isn't a good choice; as
On Wed, Aug 31, 2005 at 03:12:58PM -0700, H. Peter Anvin wrote:
> Well, we have initramfs for the really big stuff. The kernel
> shouldn't really need that much data, though.
except the initrd image is in many cases fairly fixed; right now i
have options i pass into initramfs by passing argument
Hi,
On Wed, 31 Aug 2005, Perez-Gonzalez, Inaky wrote:
> + flags = tp->clock_id & TIMEOUT_FLAGS_MASK;
> + clock_id = tp->clock_id & TIMEOUT_CLOCK_MASK;
> +
> + result = -EINVAL;
> + if (flags & ~TIMEOUT_RELATIVE)
> + goto out;
> +
> + /* someday, we should support *all*
On 9/1/05, Chris Wedgwood <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 31, 2005 at 03:01:57PM -0700, H. Peter Anvin wrote:
>
> > Maybe not. Another option would simply be to bump it up
> > significantly (2x isn't really that much.) 4096, maybe.
>
> I wonder if we're not at the point where we need s
On Wed, Aug 31, 2005 at 03:01:57PM -0700, H. Peter Anvin wrote:
> Maybe not. Another option would simply be to bump it up
> significantly (2x isn't really that much.) 4096, maybe.
I wonder if we're not at the point where we need something different
to what we have now. The concept of a command
Joe Korty wrote:
The returned timeout struct has a bit used to mark the value as absolute. Thus
the caller treats the returned timeout as a opaque cookie that can be
reapplied to the next (or more likely, the to-be restarted) timeout.
Okay, endtime is always absolute value of when it should h
Chris Wedgwood wrote:
On Wed, Aug 31, 2005 at 02:29:44PM -0700, H. Peter Anvin wrote:
I think someone on the SYSLINUX mailing list already sent a patch to
akpm to make 512 the default; making it configurable would be a
better idea. Feel free to send your patch through me.
So we really need t
This patch makes relayfs_remove use simple_rmdir for removing
directories instead of simple_unlink. Thanks to Nathan Scott for the
original patch.
Andrew, please apply.
Thanks,
Tom
Signed-off-by: Tom Zanussi <[EMAIL PROTECTED]>
diff -urpN -X dontdiff linux-2.6.13-rc6-mm2/fs/relayfs/inode.c
l
On Thu, 1 Sep 2005, Nick Piggin wrote:
Holger Kiehl wrote:
meminfo.dump:
MemTotal: 8124172 kB
MemFree: 23564 kB
Buffers: 7825944 kB
Cached: 19216 kB
SwapCached: 0 kB
Active: 25708 kB
Inactive: 7835548 kB
HighTotal:
On Wed, Aug 31, 2005 at 02:29:44PM -0700, H. Peter Anvin wrote:
> I think someone on the SYSLINUX mailing list already sent a patch to
> akpm to make 512 the default; making it configurable would be a
> better idea. Feel free to send your patch through me.
So we really need this to be a configur
This patch fixes a bug in kprobes's handling of a corner case on i386
and x86_64. On an SMP system, if one CPU unregisters a kprobe just
after another CPU hits that probepoint, kprobe_handler() on the latter
CPU sees that the kprobe has been unregistered, and attempts to let the
CPU continue as if
This highly technical change allows the kernel to jump atop the Eiffel Tower,
fly with acceleration fifty times that of a space shuttle, and ingest 15 times
its own weight.
Patch-subject: Whitespace cleanup in pageattr.c
Depends-on: add-pgtable-allocation-notifiers
Signed-off-by: Zachary Amsden <[
Ok, the use of "1 + " and subtraction of one for PAE PDPEs has confused
many people now. Make it explicit what is going on and why anding with
PAGE_MASK is a better idea to strip these bits.
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Depends-on: add-pgtable-allocation-notifiers
Index: linu
On Wednesday, 31 August 2005, at 11:27:41 -0600,
Jeff V. Merkey wrote:
> I am very open to discussions of this. Please go ahead and argue the
> merits of GPL vs. proprietary code. DSFS is platform
> neutral and will also run on Windows XP/2000/2003/Longhorn and Free BSD.
> It uses no kernel head
Not very much of importance here, but the idea for these cleanups
came along during discussion of my last set of patches with Chris
Wright.
One cleans up whitespace, another improves understandability of
the mysterious +/- 1's in the page table init code.
Zachary Amsden <[EMAIL PROTECTED]>
-
To u
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the heading of "derived work".
Also note that the GPL below is copyrighted by the Free Software
Foundation, but the i
1 - 100 of 317 matches
Mail list logo
