Repeat after me Cris developers.. "Size, then flags." :-)
aacraid suffers the same affliction. Yay for type-unsafe interfaces.
Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
--- 2.6-mm/arch/cris/arch-v32/mm/intmem.c~ 2005-07-09 00:13:54 -04:00
+++ 2.6-mm/arch/cris/arch-v32/mm/intmem.c
On Fri, Jul 08 2005, Steven Pratt wrote:
> Jens Axboe wrote:
>
> >On Fri, Jul 08 2005, Andrew Morton wrote:
> >
> >
> >>Jens Axboe <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>Some more investigation - it appears to be broken read-ahead, actually.
> >>>hdparm does repeated read(), lseek() loops
I've got a Mandrake 10.0 system with a 2.6.12 kernel presently.
Somewhere between 2.6.11 and 2.6.12, /sbin/cardmgr from the
pcmcia-cs-3.2.5-3mdk package decided it needs to consume incredible
amounts of CPU time when invoked the first time following a boot.
You can definitely notice the load on
Anton wrote:
> We've had customer situations where that information would have been
> very useful.
I haven't looked closely, but when I provoked the oom killer last week
a few times while working on something else, I did notice that the
printk's that came out were a page or two, per kill.
On Thu, Jul 07, 2005 at 09:30:21PM +0200, Stefan Richter wrote:
> Jody McIntyre wrote:
> >On Mon, Jul 04, 2005 at 01:24:05AM +0200, Adrian Bunk wrote:
> >>What shall I do?
> >>- resend this patch with the removal date set to August or
> >
> >That should be fine. I'll watch for it this time.
This patch contains the following possible cleanups:
- make two needlessly global structs static
- #if 0 the EXPORT_SYMBOL'ed but unused function tveeprom_dump
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 19 Apr 2005
drivers/media/video/tveeprom.c |
On Thu, Jun 02, 2005 at 05:12:50PM -0400, Dave Jones wrote:
> On Thu, Jun 02, 2005 at 10:48:14PM +0200, Adrian Bunk wrote:
> > On Sat, May 07, 2005 at 03:45:07PM +0200, Andi Kleen wrote:
> > > On Fri, May 06, 2005 at 11:19:14PM +0200, Adrian Bunk wrote:
> > > > Back in January, Andi Kleen added
On Mon, Jul 04, 2005 at 08:27:56PM +0200, Roman Zippel wrote:
>...
> config IP_FIB_HASH
> def_bool ASK_IP_FIB_HASH || !IP_ADVANCED_ROUTER
An updated patch is below.
> bye, Roman
cu
Adrian
<-- snip -->
This patch fixes the following kconfig warning:
net/ipv4/Kconfig:92:warning:
This patch contains the following possible cleanups:
- make the following needlessly global function static:
- irnet/irnet_ppp.c: irnet_init
- remove the following unneeded EXPORT_SYMBOL's:
- irlmp.c: sysctl_discovery_timeout
- irlmp.c: irlmp_reasons
- irlmp.c: irlmp_dup
- irqueue.c:
gcc correctly complained about a division by zero for HZ < 1000.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 2 Jul 2005
--- linux-2.6.13-rc1-mm1-full/drivers/net/wireless/ipw2200.c.old
2005-07-02 23:14:39.0 +0200
+++
On Sat, Jul 09, 2005 at 04:07:18AM +0200, Adrian Bunk wrote:
> On Thu, Jul 07, 2005 at 04:00:37AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.13-rc1-mm1:
> >...
> > +gregkh-driver-speakup-docs.patch
> > +gregkh-driver-speakup-core.patch
> >
> > driver-core updates
> >...
>
> These
David Lang wrote:
> On Fri, 8 Jul 2005, Ed Tomlinson wrote:
>
>>
>> No Flame from me. One thing to remember is that Hans and friends _have_
>> supported
>> R3 for years. This is an undisputed fact. Second third parties have be
>> able to add much
>> function (like journaling) to R3 so the
Do you know if there is a way to tell the ehci driver to do the DMA at a
lower memory address? i.e. tell the kernel to reserve a block of memory (as
a boot option) and then tell the ehci driver to use that area of RAM
instead?
Thanks again for your help,
Jon
From: Andi Kleen <[EMAIL
On Fri, Jul 08, 2005 at 05:54:48PM -0500, Matt Domsch wrote:
> Greg,
>
> The below patch is a first pass at implementing subclasses, for review
> and comment.
>
> As a test, I modified drivers/input/input.c to allocate a new class,
> and register it as a subclass.
>
> Before:
>
>
> Unable to handle kernel paging request at virtual address 762f7473
> printing eip:
> c0183c14
> *pde =
> Oops: 0002 [#1]
> PREEMPT
> Modules linked in: rtc nls_utf8 snd_emu10k1_synth snd_emu10k1
> snd_emux_synth snd_seq_virmidi snd_rawmidi snd_pcm_oss snd_ac97_codec
>
Hello,
Im looking for some help on some research I am conducting. Im trying
to understand the complete execution process from start to finish of
an ELF executable object on the i386 platform in particular, but
x86_64 works as well. So far I have come up with the following:
Shell passes arguments
On 7/8/05, Chris Wright <[EMAIL PROTECTED]> wrote:
> * Timothy R. Chavez ([EMAIL PROTECTED]) wrote:
> > @@ -69,6 +70,8 @@ int inode_setattr(struct inode * inode,
> > unsigned int ia_valid = attr->ia_valid;
> > int error = 0;
> >
> > + audit_notify_watch(inode, MAY_WRITE);
> > +
>
On Thu, Jul 07, 2005 at 04:00:37AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc1-mm1:
>...
> +gregkh-driver-speakup-docs.patch
> +gregkh-driver-speakup-core.patch
>
> driver-core updates
>...
These aren't driver-core updates, these are new drivers.
It seems I missed when this was
Hi,
Signed-off-by: Albert Herranz
<[EMAIL PROTECTED]>
The following patch prevents the crash dump helper
code found within kexec from breaking ppc which still
lacks crash dump functionality.
As discussed in [1], ksysfs crash_notes attribute
handling was left under CONFIG_KEXEC for simplicity
/proc/$pid/smaps code was based on the old ptwalking style just as we
converted over to the p?d_addr_end style: convert it to the new style.
Do an easy cond_resched_lock at the end of each page table: looking at
the struct page of every pte will be heavy on the cache, and others are
likely to
/proc/$pid/smaps show_smap has followed show_map in using variable name
"map" where we would usually say "vma": change them to "vma" throughout.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
fs/proc/task_mmu.c | 98 ++---
1 files changed,
This patch fixes an obvious typo (DCHP->DHCP).
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 26 Jun 2005
--- linux-2.6.12-mm2-full/Documentation/kernel-parameters.txt.old
2005-06-26 14:36:44.0 +0200
+++
inotify
Documentation/filesystems/inotify.txt | 155 +
fs/Kconfig| 13
fs/Makefile |1
fs/inode.c|6
fs/inotify.c | 1011 ++
Add fsnotify as infrastructure for various fs notifcation schemes.
Move dnotify to fsnotify.
fs/attr.c| 33 +
fs/compat.c | 12 +++-
fs/file_table.c |3 +
fs/namei.c | 30 ++-
fs/nfsd/vfs.c|6 +-
The following two patches simply split fsnotify from inotify.
There should be no functional change to inotify at all. Perhaps the
split will help identify the interface bits that can easily converge
for inotify and audit. They're completely untested... I started with
inotify-45 in
On Sat, Jul 09, 2005 at 01:36:08AM +0200, Roman Zippel wrote:
> Hi,
>
> On Fri, 8 Jul 2005, Adrian Bunk wrote:
>
> > --- linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig.old 2005-07-02
> > 21:57:40.0 +0200
> > +++ linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig 2005-07-02
> >
- Card definitions updated.
- Tail spaces removed.
- Mark all 7135 cards as 7133.
- Correct info about sync byte for MPEG-2 transport stream packets.
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
Signed-off-by: hermann pitton <[EMAIL
Missing attachment herein included.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || [EMAIL PROTECTED] || 1-866-677-4546
L M B E N C H 2 . 0 S U M M A R Y
- Removed unused structures.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux/drivers/media/video/bt832.c | 12
1 files changed, 12 deletions(-)
diff -u linux-2.6.13/drivers/media/video/bt832.c linux/drivers/media/video/bt832.c
---
* Timothy R. Chavez ([EMAIL PROTECTED]) wrote:
> @@ -69,6 +70,8 @@ int inode_setattr(struct inode * inode,
> unsigned int ia_valid = attr->ia_valid;
> int error = 0;
>
> + audit_notify_watch(inode, MAY_WRITE);
> +
Hmm, this looks wrong. It should be in notify_change, since
Three of the four BUG_ONs in delete_from_swap_cache are immediately
repeated in __delete_from_swap_cache: delete those and add the one.
But perhaps mm/ is altogether overprovisioned with historic BUGs?
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
mm/swap_state.c |6 +-
1 files
- Removed unused structures.
- CodingStyle rules applied to comments.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux/drivers/media/video/msp3400.c | 30 +++-
linux/drivers/media/video/tda7432.c | 13
linux/drivers/media/video/tda9875.c |
Remove the three get_mm_counter(mm, rss) tests from rmap.c: there was a
time when testing rss was important to avoid a particular race between
dup_mmap and the anonmm rmap; but now it's just a rather silly pseudo-
optimization, made even more obscure by the get_mm_counter macro.
Signed-off-by:
- Eliminated unused code.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux/drivers/media/video/tveeprom.c |9 +
1 files changed, 1 insertion(+), 8 deletions(-)
diff -u linux-2.6.13/drivers/media/video/tveeprom.c linux/drivers/media/video/tveeprom.c
---
- obsolete TUNER_SET_TVFREQ changed to VIDIOCSFREQ.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux-2.6.13-rc2-mm1/drivers/media/video/tuner-3036.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.13-rc2-mm1/drivers/media/video/tuner-3036.c.orig
On Fri, Jul 08, 2005 at 08:49:12PM -0400, Jon Schindler wrote:
> Hi Andi,
>
> As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB
> storage device to work. So, to answer your question, yes, the ohci_hcd
> driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to
- Fixed a trouble on tuner-core that generates erros on computers with more
than one TV card.
- Rename tuner structures fields.
- Tail spaces removed.
- I2C cleanups and converged to a basic reference structure.
- Removed unused structures.
- Fix setting frequency on tda8290.
- Added code for
Hi Andi,
As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB
storage device to work. So, to answer your question, yes, the ohci_hcd
driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to work with
both ehci and 3GB's of RAM, so it still sounds like it's a
- driver command adapted to use new control (TUNER_SET_TYPE_ADDR,
instead of TUNER_SET_TYPE)
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux-2.6.13-rc2-mm1/drivers/media/video/mxb.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
---
- Removed obsolete option. Current code needs multi tuner.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
drivers/media/video/Kconfig | 13 -
1 files changed, 13 deletions(-)
--- linux-2.6.13-rc2-mm1/drivers/media/video/Kconfig.orig 2005-07-07 22:08:59.0 -0300
- Removed unused structures.
- CodingStyle rules applied to comments.
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux/drivers/media/common/ir-common.c | 255 ++---
1 files changed, 110 insertions(+), 145 deletions(-)
diff -u
On Fri, 8 Jul 2005, Ed Tomlinson wrote:
No Flame from me. One thing to remember is that Hans and friends _have_
supported
R3 for years. This is an undisputed fact. Second third parties have be able
to add much
function (like journaling) to R3 so the code must be sort of readable... With
- Add new Typhoon DVB-T Cardbus.
- DVB-T support for MD7134 cardbus and the PCI variants
- initial DVB-T support for Lifeview Flydvb-t duo
- DVB-T support for Philips TOUGH reference design
- Don't turn off the xtal output of tda8274/75 in sleep mode
- Let Kconfig decide whether to include
- Removed unused structures.
- Removed BTTV version check.
- Some debug structs moved to their own .c file and converted to static
- Comment changed to express better when attach_inform is running
- set_freq removed from set_mode at tuner-core.c.
- I2C cleanups and converged to a basic reference
Changes to comply with CodingStyle: // comments converted to /* */
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
linux/drivers/media/video/ir-kbd-i2c.c | 51 ++---
1 files changed, 21 insertions(+), 30 deletions(-)
diff -u
- use DMA_32BIT_MASK.
- Rename tuner structures fields.
- Tail spaces removed.
- I2C cleanups and converged to a basic reference structure.
- Removed unused structures.
- Removed BTTV version check.
Signed-off-by: <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
get_swap_page has often shown up on latency traces, doing lengthy scans
while holding two spinlocks. swap_list_lock is already dropped, now
scan_swap_map drop swap_device_lock before scanning the swap_map.
While scanning for an empty cluster, don't worry that racing tasks may
allocate what was
The swap header's unsigned int last_page determines the range of swap
pages, but swap_info has been using int or unsigned long in some cases:
use unsigned int throughout (except, in several places a local unsigned
long is useful to avoid overflows when adding).
Signed-off-by: Hugh Dickins <[EMAIL
On Friday 08 July 2005 18:59, Ed Cogburn wrote:
> [EMAIL PROTECTED] wrote:
> >
> > In reality is it doesn't count. Users don't care what level of pain is
> > involved in producing the products they use.
> >
> > Development efforts and results for OS's are always just taken for
> > granted.
> >
The "Adding %dk swap" message shows the number of swap extents, as a guide
to how fragmented the swapfile may be. But a useful further guide is what
total extent they span across (sometimes scarily large).
And there's no need to keep nr_extents in swap_info: it's unused after
the initial
Roman Zippel wrote:
Hi,
On Fri, 8 Jul 2005, Adrian Bunk wrote:
--- linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig.old 2005-07-02
21:57:40.0 +0200
+++ linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig 2005-07-02 21:58:06.0
+0200
@@ -447,7 +447,7 @@
source
Rewrite get_swap_page to allocate in just the same sequence as before,
but without holding swap_list_lock across its scan_swap_map. Decrement
nr_swap_pages and update swap_list.next in advance, while still holding
swap_list_lock. Skip full devices by testing highest_bit. Swapoff hold
The get_swap_page/scan_swap_map latency can be so bad that even those
without preemption configured deserve relief: periodically cond_resched.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
mm/swapfile.c | 14 --
1 files changed, 12 insertions(+), 2 deletions(-)
---
This makes negligible difference in practice: but swap_list.next should not
be updated to a higher prio in the general helper swap_info_get, but rather
in swap_entry_free; and then only in the case when entry is actually freed.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
mm/swapfile.c |
Aha, swsusp dips into swap_info[], better update it to swap_lock. It's
bitflipping flags with 0xFF, so get_swap_page will allocate from only
the one chosen device: let's change that to flip SWP_WRITEOK.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
kernel/power/swsusp.c | 12
The idea of a swap_device_lock per device, and a swap_list_lock over them
all, is appealing; but in practice almost every holder of swap_device_lock
must already hold swap_list_lock, which defeats the purpose of the split.
The only exceptions have been swap_duplicate, valid_swaphandles and an
Rewrite scan_swap_map to allocate in just the same way as before
(taking the next free entry SWAPFILE_CLUSTER-1 times, then restarting at
the lowest wholly empty cluster, falling back to lowest entry if none),
but with a view towards dropping the lock in the next patch.
Signed-off-by: Hugh
There are several comments that swap's extent_list.prev points to the
lowest extent: that's not so, it's extent_list.next which points to it,
as you'd expect. And a couple of loops in add_swap_extent which go all
the way through the list, when they should just add to the other end.
Fix those up,
If a regular swapfile lies on a filesystem whose blocksize is less than
PAGE_SIZE, then setup_swap_extents may have to cut the number of usable
swap pages; but sys_swapon's nr_good_pages was not expecting that. Also,
setup_swap_extents takes no account of badpages listed in the swap header:
not
sys_swapon's call to destroy_swap_extents on failure is made after the
final swap_list_unlock, which is faintly unsafe: another sys_swapon might
already be setting up that swap_info_struct. Calling it earlier, before
taking swap_list_lock, is safe. sys_swapoff's call to destroy_swap_extents
was
Update swap extents comment: nowadays we guard with S_SWAPFILE not i_sem.
Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
---
mm/swapfile.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- 2.6.13-rc2-mm1/mm/swapfile.c2005-07-07 12:33:21.0 +0100
+++
Here comes a series of 13 swap patches, mainly to mm/swapfile.c, based
on 2.6.13-rc2-mm1 but applying also to 2.6.13-rc2. I don't think any
of them are important enough for 2.6.13, though the first half are
straightforward. The main thrust is to scan the swap_map lockless,
to stop the infamous
Alexander Nyberg <[EMAIL PROTECTED]> wrote:
>
> I think we really need an option in the kernel to help users in tracking
> slab leaks so that they can be brought down easier.
Well we already have slab-leak-detector.patch, whcih I appear to have been
sitting on since 2.6.0-test8. it fell out of
Alexander Nyberg <[EMAIL PROTECTED]> wrote:
>
> +config SLAB_OWNER
> + bool "Track owner of slab objects"
> + depends on DEBUG_KERNEL && DEBUG_SLAB
I guess this should select CONFIG_KALLSYMS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
"Jon Schindler" <[EMAIL PROTECTED]> writes:
>
> This mainly seems to be an issue with USB mass storage devices like
> USB memory sticks and USB hard drives (I've tried both, and neither is
> assigned a scsi device properly). I am still able to use my USB mouse
> when I have 3GB installed. I'm
Hi,
On Fri, 8 Jul 2005, Adrian Bunk wrote:
> --- linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig.old 2005-07-02
> 21:57:40.0 +0200
> +++ linux-2.6.13-rc1-mm1/drivers/scsi/Kconfig 2005-07-02 21:58:06.0
> +0200
> @@ -447,7 +447,7 @@
> source
On Fri, 2005-07-08 at 16:29 -0700, David S. Miller wrote:
> From: "Martin J. Bligh" <[EMAIL PROTECTED]>
> Date: Fri, 08 Jul 2005 16:14:59 -0700
>
> > I'm not saying there isn't data supporting higher HZ ... I just haven't
> > seen it published. I get the feeling what people really want is
Hi,
On Fri, 2005-07-08 at 21:11 +0200, Roman Zippel wrote:
> So it basically comes down to personal preference, if the original uses
> defines and it works fine, I don't really see a good enough reason to
> change it to enums, so please leave the decision to author.
(And I don't see a good
Quoting Tony Jones ([EMAIL PROTECTED]):
> Hey Serge,
> Seemed useful to be able to view which modules had been unloaded.
> Easier to maintain them on their own list than to compute the difference
> of and . Patch attached, not sure if you
> are cool with reusing the 'unload' file.
Attached is a
From: "Martin J. Bligh" <[EMAIL PROTECTED]>
Date: Fri, 08 Jul 2005 16:14:59 -0700
> I'm not saying there isn't data supporting higher HZ ... I just haven't
> seen it published. I get the feeling what people really want is high-res
> timers anyway ... high HZ is just concealing the issue and
Bob Picco <[EMAIL PROTECTED]> writes:
> We have a requirement on IA64 to run the ACPI interpreter in the setup_arch
> function before paging_init examines the maximum DMA physical address which
> is limited by the IOMMU. One obstacle is the use of kmalloc/kfree by
> ACPI. Using the bootmem
On Mon, Jul 04, 2005 at 04:59:18PM +0200, Bodo Eggert wrote:
> --- Documentation/kbuild/kconfig-language.txt ---
> - input prompt: "prompt" ["if" ]
> Every menu entry can have at most one prompt, which is used to display
> to the user. Optionally dependencies only for this prompt can be added
Document that udev 058 is required.
A similar patch (that no longger applies due to unrelated context
changes) was sent by Jesper Juhl.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 2 Jul 2005
--- linux-2.6.13-rc1-mm1-full/Documentation/Changes.old
On 7/8/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > @@ -655,7 +655,7 @@ i2QueueCommands(int type, i2ChanStrPtr p
> > timeout--; // So negative values == forever
> >
> > if (!in_interrupt()) {
>
> I worry about what this
>I don't see how the following is tortured:
>
>enum {
> PNODE_MEMBER_VFS = 0x01,
> PNODE_SLAVE_VFS = 0x02
>};
Only because it's using a facility that's supposed to be for enumerated
types for something that isn't. If it were a true enumerated type, the
codes for the
Greg,
The below patch is a first pass at implementing subclasses, for review
and comment.
As a test, I modified drivers/input/input.c to allocate a new class,
and register it as a subclass.
Before:
/sys/class/input/
/sys/class/input_device/
After:
/sys/class/input/input_device/
In this pass
--On Friday, July 08, 2005 16:03:03 -0700 Chris Wedgwood <[EMAIL PROTECTED]>
wrote:
> On Fri, Jul 08, 2005 at 03:59:35PM -0700, Martin J. Bligh wrote:
>
>> I think we're talking between 2.6.12-git5 and 2.6.12-git6 right? I
>> can confirm more explicitly if really need be. 48s -> 45.5s
> > Time started to pass faster with 2.6.12.2 (actually, it was 2.6.12-ck3
> > which is based on it). I have isolated the cause of the problem:
>
> I bet you this fixes it (already in mainline)
> [...]
Indeed it does. Thanks.
Rudo.
-
To unsubscribe from this list: send the line "unsubscribe
[EMAIL PROTECTED] wrote:
>
> @@ -655,7 +655,7 @@ i2QueueCommands(int type, i2ChanStrPtr p
> timeout--; // So negative values == forever
>
> if (!in_interrupt()) {
I worry about what this driver is trying to do...
> -
On Fri, Jul 08, 2005 at 03:59:35PM -0700, Martin J. Bligh wrote:
> I think we're talking between 2.6.12-git5 and 2.6.12-git6 right? I
> can confirm more explicitly if really need be. 48s -> 45.5s elapsed.
That's a huge difference (5%) --- what hardware is that on?
-
To unsubscribe from this
> It's been over two weeks and nobody has complained about anything.
>
>>
>> > [PATCH] i386: Selectable Frequency of the Timer Interrupt
>>
>> [...]
>>
>> > +choice
>> > + prompt "Timer frequency"
>> > + default HZ_250
>>
>> WHAT?
>>
>> The previous value here i386 is 1000 --- so why is
* Lee Revell ([EMAIL PROTECTED]) wrote:
> I think it's already queued for -stable.
Yes, it is.
-
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
[EMAIL PROTECTED] wrote:
>
> In reality is it doesn't count. Users don't care what level of pain is
> involved in producing the products they use.
>
> Development efforts and results for OS's are always just taken for
> granted.
>
> BTDT - if you're very lucky, a (very) few non-programming
Sysfs Gurus,
I want to export few driver specific sysfs attributes when my driver loads.
This driver is a pci hotplug driver. I want to export these sysfs attributes
as soon as my pci_module_init succeeds.
1. I see that there is /sys/modules directory lists all the modules. Is this
a right place
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> Quoting Tony Jones ([EMAIL PROTECTED]):
> Attached is a patch to re-introduce the necessary locking to allow
> unloading of LSMs. I don't have any performance results nor hardcore
> stability tests yet.
And here is a patch on top of that to use
On Fri, Jul 08, 2005 at 05:46:35PM -0500, Adnan Khaleel wrote:
> Andi,
>
> Would it be possible for you to send me the source to the single stepping
> code. It may be
> too slow but it might prove to be sufficient for some simple benchmarks I
> guess.
Andi,
Would it be possible for you to send me the source to the single stepping code.
It may be
too slow but it might prove to be sufficient for some simple benchmarks I guess.
Thanks a million.
Adnan
-Original Message-
From: Andi Kleen [mailto:[EMAIL PROTECTED]
Sent: Friday, July 08,
Jeremy Nickurak wrote:
> On ven, 2005-07-08 at 03:22 +0200, Bernd Eckenfels wrote:
> > No, it is creating files by appending just like any other file write. One
> > could think about a call to create unfragmented files however since this is
> > not always working best is to create those files
Hi.
On Fri, 2005-07-08 at 23:30, Stefan Seyfried wrote:
> Matthew Garrett wrote:
>
> > Right, so you support the resume from disk trigger in sysfs and the
> > /proc/acpi/sleep interface? If suspend2 is a complete dropin replacement
> > then I'm much happier with the idea of dropping swsusp, but
Lee Revell <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2005-07-08 at 14:59 -0700, Andrew Morton wrote:
> > Chris Wedgwood <[EMAIL PROTECTED]> wrote:
> > >
> > > On Thu, Jun 23, 2005 at 11:28:47AM -0700, Linux Kernel Mailing List wrote:
> > ^^
> >
> > It's been over two weeks and nobody
Hi Ingo,
More SMT weirdness. Latency traces aren't looking quite right on -51-17
with my SMT debug config.
Started jackd, immediately after boot (before logging in to X), then:
[EMAIL PROTECTED] ~]# cat /proc/latency_trace
cat/2149[CPU#1]: BUG in update_out_trace at kernel/latency.c:698
[]
On Sat, Jul 09, 2005 at 12:02:45AM +0200, Peter Osterlund wrote:
> Hi,
>
> The help text for SERIO_RAW refers to the wrong sysfs device node.
> This patch fixes it.
>
> Signed-off-by: Peter Osterlund <[EMAIL PROTECTED]>
> ---
This patch is already in my queue, from Neil Brown.
>
On Fri, 2005-07-08 at 15:03 -0700, Phil Oester wrote:
> On Fri, Jul 08, 2005 at 11:25:08PM +0200, Alexander Nyberg wrote:
> > fre 2005-07-08 klockan 23:12 +0200 skrev Rudo Thomas:
> > > Hello, guys.
> > >
> > > Time started to pass faster with 2.6.12.2 (actually, it was 2.6.12-ck3
> > > which is
On Fri, Jul 08, 2005 at 02:54:07PM -0500, [EMAIL PROTECTED] wrote:
> > Also, why not just add the hotplug flag to the firmware structure?
> That
> request_firmware kmalloc's the firmware structure and frees it when
> returned. The only way to indicate request_firmware to skip hotplug was
> by
Jens Axboe wrote:
On Fri, Jul 08 2005, Andrew Morton wrote:
Jens Axboe <[EMAIL PROTECTED]> wrote:
Some more investigation - it appears to be broken read-ahead, actually.
hdparm does repeated read(), lseek() loops which causes the read-ahead
logic to mark the file as being in cache
On Fri, 2005-07-08 at 14:59 -0700, Andrew Morton wrote:
> Chris Wedgwood <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, Jun 23, 2005 at 11:28:47AM -0700, Linux Kernel Mailing List wrote:
> ^^
>
> It's been over two weeks and nobody has complained about anything.
Wrong, I complained
Hi,
The help text for SERIO_RAW refers to the wrong sysfs device node.
This patch fixes it.
Signed-off-by: Peter Osterlund <[EMAIL PROTECTED]>
---
linux-petero/drivers/input/serio/Kconfig |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN
In article <[EMAIL PROTECTED]>,
Adnan Khaleel <[EMAIL PROTECTED]> wrote:
>Thanks for your suggestions. I have been working with Simics, SimNow and
>Bochs. I've had mixed luck with all of them. Although Simics should be
>the most promising, I've really had
>an uphill struggle with it especially
On Fri, Jul 08, 2005 at 11:25:08PM +0200, Alexander Nyberg wrote:
> fre 2005-07-08 klockan 23:12 +0200 skrev Rudo Thomas:
> > Hello, guys.
> >
> > Time started to pass faster with 2.6.12.2 (actually, it was 2.6.12-ck3
> > which is based on it). I have isolated the cause of the problem:
>
> I bet
This patch contains the following fixes:
- IBM_ASM must depend on PCI
- remove useless "default n"
- correct the URL to further information
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 1 Jul 2005
--- linux-2.6.12-mm2-full/drivers/misc/Kconfig.old
1 - 100 of 669 matches
Mail list logo
