On Tue, 1 Feb 2005 03:28:31 +, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> diff -buprN -X dontdiff
> vanilla-2.6.11-rc2-bk9/arch/um/os-Linux/drivers/tuntap_user.c
> linux-2.6.11-rc2-bk9/arch/um/os-Linux/drivers/tuntap_user.c
> ---
Itsuro Oda wrote:
Hi,
I can't understand why ELF format is necessary.
I think the only necessary information is "what physical address
regions are valid to read". This information is necessary for any
sort of dump tools. (and must get it while the system is normal.)
The Eric's /proc/cpumem idea
Hi,
I don't like calling crash_kexec() directly in (ex.) panic().
It should be call_dump_hook() (or something like this).
I think the necessary modifications of the kernel is only:
- insert the hooks that calls a dump function when crash occur
- binding interface that binds a dump function to
On 30 Jan 2005 12:10:34 +0100, Peter Osterlund <[EMAIL PROTECTED]> wrote:
> > - Slow motion of finger produces no motion, then a jump. So, it's very hard
> > to
> > target smaller UI elements and some web links.
>
> I see this too when I don't use the X touchpad driver. With the X
> driver
At some point in time, I wrote:
> > kstrdup() is a special-case _memory allocator_ (not so much a string
> > operation) so I think it should go into mm/slab.c where we currently
> > have kcalloc().
On Tue, 01 Feb 2005 17:00:17 +, Paulo Marques <[EMAIL PROTECTED]> wrote:
> I was following
On 032, 02 01, 2005 at 10:02:41AM -0800, Pete Zaitcev wrote:
> Hi, guys,
>
> I was looking at this:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=138892
>
> I have added usb-handoff as a kernel option in grub.conf for
> 2.4.21-20.EL (smp) and re-enabled USB Emulation and
[EMAIL PROTECTED] wrote:
Koichi Suzuki <[EMAIL PROTECTED]> writes:
Hook in panic code is very good idea and is useful in various scenes. It could
be used to kick RAM dump code, obviously, and also kick the code to initiate
failover, etc. Various use could be possible so I believe that this hook
Hi,
I can't understand why ELF format is necessary.
I think the only necessary information is "what physical address
regions are valid to read". This information is necessary for any
sort of dump tools. (and must get it while the system is normal.)
The Eric's /proc/cpumem idea sounds nice to
On Tue, Feb 01, 2005 at 02:05:52PM -0800, Greg KH wrote:
> On Wed, Jan 12, 2005 at 02:48:36PM +0200, Paul Mundt wrote:
> > Yes, it would seem that way. Here we go again:
> >
> > drivers/sh/Makefile |6
> > drivers/sh/superhyway/Makefile |7 +
> >
* Lee Revell <[EMAIL PROTECTED]> wrote:
> OK. Rereading my old mail, it looks like there were some possibly
> unresolved false positives with the userspace atomicity debugger.
>
> Here's one I get from alsaplayer. Would more information be required
> to know if this is a false positive?
this
On Tue, Feb 01, 2005 at 02:30:08PM -0800, Greg KH wrote:
> On Tue, Feb 01, 2005 at 11:23:27PM +0100, Sam Ravnborg wrote:
> > On Tue, Feb 01, 2005 at 02:05:52PM -0800, Greg KH wrote:
> > > > drivers/sh/Makefile |6
> > > > drivers/sh/superhyway/Makefile |7 +
Hi Andrew,
I've had this patch reviewed by Jens, and
incorporated his recommended fixes. This patch applies
to the latest bk tree.
The patch adds new interfaces to bio.c that support
the creation of local bio and bvec pools. This is
important for layered drivers that need to allocate
new bio
On Tue, Feb 01, 2005 at 09:34:59PM -0500, Timothy Miller wrote:
> Basically, I get random poppling and crackling noises out of my
> speakers. Sometimes it's silent, and sometimes, it crackles and pops
> for minutes at a time. It's really disturbing, really, because it
> happens suddenly,
On Wednesday 02 February 2005 01:08, Victor Hahn wrote:
> Dmitry Torokhov wrote:
>
> >Any luck with the patch?
> >
>
> I'm using 2.6.11rc2 with the patch for some hours now and it seems as if
> it doesn't throw away bytes any more which makes linux 2.6 useable for
> me again - thanks a lot!
This patch adds so-called "usbmon", or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission and giveback paths even when not monitoring, but this
was deemed a
Nobody answered so i repeat the question.
I think i found a way to make use of NLS table for HFS filesystem and
i'm going to try to implement it. But first i need to create NLS module
for codepage 10007 (Mac cyrillic). In the beginning of every existing
NLS module code i see comment which says
Dmitry Torokhov wrote:
Any luck with the patch?
I'm using 2.6.11rc2 with the patch for some hours now and it seems as if
it doesn't throw away bytes any more which makes linux 2.6 useable for
me again - thanks a lot! I just encountered one smaller issue (this
really is much better than before):
On Tue, Feb 01, 2005 at 09:34:59PM -0500, Timothy Miller wrote:
> Basically, I get random poppling and crackling noises out of my
> speakers. Sometimes it's silent, and sometimes, it crackles and pops
> for minutes at a time. It's really disturbing, really, because it
> happens suddenly,
On Tue, 01 Feb 2005 22:37:50 +0100, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> I think if cat is the prefered tool for viewing this file then it should
> be more human readable. If not, then a binary format should be choosen.
> Maybe we can implement both. Is this possible?
Yes. Now you know
applied
-
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/
Ingo,
I hope we can get past this anger and continue working together. We
have too much to gain by cooperating. It would be a shame to let hurt
feelings get in the way for either of us.
> * Jack O'Quin <[EMAIL PROTECTED]> wrote:
>> Well, this extremely long discussion started with a request
Zhonglin Zhang <[EMAIL PROTECTED]> wrote:
>
> Hi, Andrew
>
> Could you please check it ? I have worked out my little patch to fix
> it. But not any feedback. Is it ok in your machine which is not-SMP?
>
--- 25/include/linux/stop_machine.h~fix-kallsyms-insmod-rmmod-race-fix-fix-fix
On Tue, 2005-02-01 at 14:22 -0800, Randy.Dunlap wrote:
> Chris Wedgwood wrote:
> > On Mon, Jan 31, 2005 at 01:34:59AM -0600, Matt Mackall wrote:
> >
> >
> >>+#define qsort xfs_sort
> >>+static inline void xfs_sort(void *a, size_t n, size_t s,
> >>+ int (*cmp)(const void *,const
> 18_ide_comment_fixes.patch
>
> Comment fixes.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-dma.c
===
--- linux-ide-export.orig/drivers/ide/ide-dma.c 2005-02-02 10:27:15.202313614
On Wed, 2 Feb 2005, Nick Piggin wrote:
> Well yeah, but the interesting case is when that isn't a lock ;)
>
> I'm not saying what you've got is no good. I'm sure it would be fine
> for testing. And if it happens that we can do the "page_count doesn't
> mean anything after it has reached zero and
> 09_ide_do_rw_disk_lba48_dma_check_fix.patch
>
> In __ide_do_rw_disk(), the shifted block, instead of the
> original rq->sector, should be used when checking range for
> lba48 dma.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-disk.c
> 07_ide_reg_valid_t_endian_fix.patch
>
> ide_reg_valid_t contains bitfield flags but doesn't reverse
> bit orders using __*_ENDIAN_BITFIELD macros. And constants
> for ide_reg_valid_t, IDE_{TASKFILE|HOB}_STD_{IN|OUT}_FLAGS,
> are defined as byte values which are correct
> 10_ide_do_rw_disk_pre_task_out_intr_return_fix.patch
>
> In __ide_do_rw_disk(), ide_started used to be returned blindly
> after issusing PIO write. This can cause hang if
> pre_task_out_intr() returns ide_stopped due to failed
> ide_wait_stat() test. Fixed to pass the
> 19_ide_diag_taskfile_use_init_drive_cmd.patch
>
> In ide_diag_taskfile(), when initializing taskfile rq,
> ref_count wasn't initialized properly. Modified to use
> ide_init_drive_cmd(). This doesn't really change any behavior
> as the request isn't managed via the
Since it looks like ide is being worked on, can you convert ide to use
the PCI ROM access calls in drivers/pci/rom.c instead of directly
manipulating PCI config space? The new ROM calls work on all
architectures.
These are the places that need to be fix:
[EMAIL PROTECTED] ide]$ grep -r
> 11_ide_drive_sleeping_fix.patch
>
> ide_drive_t.sleeping field added. 0 in sleep field used to
> indicate inactive sleeping but because 0 is a valid jiffy
> value, though slim, there's a chance that something can go
> weird. And while at it, explicit jiffy comparisons
On Wed, 02 Feb 2005 13:55:23 +1100, Lincoln Dale <[EMAIL PROTECTED]> wrote:
> At 01:34 PM 2/02/2005, Timothy Miller wrote:
> >I've mentioned this problem before. It seemed to go away around the
> >2.6.8 timeframe, but when I started using 2.6.9, it came back. I'm
> >using 2.6.10, and it's still
On Tue, 2005-02-01 at 22:42 -0500, Joseph Fannin wrote:
> On Tue, Feb 01, 2005 at 10:18:33AM +1100, Benjamin Herrenschmidt wrote:
> > On Mon, 2005-01-31 at 06:21 -0500, Joseph Fannin wrote:
> >
> > > I'm getting a blank screen with radeonfb on two boxes here as
> > > well. One is a beige g3,
> 12_ide_hwgroup_t_polling.patch
>
> ide_hwgroup_t.polling field added. 0 in poll_timeout field
> used to indicate inactive polling but because 0 is a valid
> jiffy value, though slim, there's a chance that something
> weird can happen.
Signed-off-by: Tejun Heo <[EMAIL
On Tue, Feb 01, 2005 at 10:18:33AM +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2005-01-31 at 06:21 -0500, Joseph Fannin wrote:
>
> > I'm getting a blank screen with radeonfb on two boxes here as
> > well. One is a beige g3, the other is i386; both have PCI Radeon 7000s
> > with radeonfb
> 13_ide_tape_time_after.patch
>
> Explicit jiffy comparision converted to time_after() macro.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-tape.c
===
---
At 01:34 PM 2/02/2005, Timothy Miller wrote:
I've mentioned this problem before. It seemed to go away around the
2.6.8 timeframe, but when I started using 2.6.9, it came back. I'm
using 2.6.10, and it's still happening.
almost identical system here, other than i'm using an ASUS A7V600
> 29_ide_explicit_TASKFILE_NO_DATA.patch
>
> Make data_phase explicit in NO_DATA cases.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-disk.c
===
---
> 17_ide_flagged_taskfile_select_check.patch
>
> In flagged_taskfile(), tf_out_flags.b.select should be checked
> before using bits inside taskfile->device_head. When user
> haven't specified the select register, the default
> drive->select.all value should be used.
> 15_ide_flagged_taskfile_data_byte_order_fix.patch
>
> In flagged_taskfile(), when writing data register,
> taskfile->data goes to the lower byte and hobfile->data goes
> to the upper byte on little endian machines and the opposite
> happens on big endian machines. This
> 27_ide_remove_cmd.patch
>
> Removed unused REQ_DRIVE_CMD handling.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-io.c
===
--- linux-ide-export.orig/drivers/ide/ide-io.c 2005-02-02
Sorry, this is the same 08 patch with the correct subject line.
> 08_ide_do_identify_model_string_termination.patch
>
> Terminates id->model string before invoking strstr() in
> do_identify().
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index:
> 26_ide_taskfile_cmd_ioctl.patch
>
> ide_cmd_ioctl() converted to use ide_taskfile_ioctl(). This
> is the last user of REQ_DRIVE_CMD.
Index: linux-ide-export/drivers/ide/ide-iops.c
===
---
Jeff,
Here is the cleaned up patch (as you suggested)
that enables ata_piix to work in RAID mode on ICH6R.
I tested it and it seems to behave correctly
in all the modes---sees all 4 disks in IDE and RAID modes,
doesn't see any in Compatibility mode (which is right,
because only two are
> 23_ide_taskfile_task_ioctl.patch
>
> ide_task_ioctl() modified to map to ide_taskfile_ioctl().
> This is the last user of REQ_DRIVE_TASK.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-taskfile.c
> 24_ide_remove_task.patch
>
> Unused REQ_DRIVE_TASK handling removed.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-io.c
===
--- linux-ide-export.orig/drivers/ide/ide-io.c 2005-02-02
> 22_ide_taskfile_flush.patch
>
> All REQ_DRIVE_TASK users except ide_task_ioctl() converted
> to use REQ_DRIVE_TASKFILE.
> 1. idedisk_issue_flush() converted to use REQ_DRIVE_TASKFILE.
> This and the changes in ide_get_error_location() remove a
> possible race
> 25_ide_taskfile_cmd.patch
>
> All in-kernel REQ_DRIVE_CMD users except for ide_cmd_ioctl()
> converted to use REQ_DRIVE_TASKFILE.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-disk.c
On Tue, 2005-02-01 at 18:49 -0800, Christoph Lameter wrote:
> On Wed, 2 Feb 2005, Nick Piggin wrote:
>
> > Well yeah, but the interesting case is when that isn't a lock ;)
> >
> > I'm not saying what you've got is no good. I'm sure it would be fine
> > for testing. And if it happens that we can
> 28_ide_taskfile_init_drive_cmd.patch
>
> ide_init_drive_cmd() now initializes rq->flags to
> REQ_DRIVE_TASKFILE.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-disk.c
===
---
> 20_ide_task_end_request_fix.patch
>
> task_end_request() modified and made global. ide_dma_intr()
> modified to use task_end_request(). These changes enable
> TASKFILE ioctls to get valid register outputs on successful
> completion. No in-kernel usage should be
> 21_ide_do_taskfile.patch
>
> Merged do_rw_taskfile() and flagged_taskfile() into
> do_taskfile(). During the merge, the following changes took
> place.
> 1. flagged taskfile now honors HOB feature register.
> (do_rw_taskfile() did write to HOB feature.)
>
> 14_ide_error_remove_NULL_test.patch
>
> In ide_error(), drive cannot be NULL. ide_dump_status() can't
> handle NULL drive.
Index: linux-ide-export/drivers/ide/ide-io.c
===
---
> 16_ide_flagged_taskfile_select_dev_bit_masking.patch
>
> In flagged_taskfile(), make off DEV bit before OR'ing it with
> drive->select.all when writing to IDE_SELECT_REG.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-taskfile.c
> 08_ide_do_identify_model_string_termination.patch
>
> Terminates id->model string before invoking strstr() in
> do_identify().
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-probe.c
> 06_ide_start_request_IDE_CONTROL_REG.patch
>
> Replaced HWIF(drive)->io_ports[IDE_CONTROL_OFFSET] with
> equivalent IDE_CONTROL_REG in ide-io.c.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index: linux-ide-export/drivers/ide/ide-io.c
> 04_ide_cleanup_piix.patch
>
> In drivers/ide/pci/piix.[hc], init_setup_piix() is defined and
> used but only one init_setup function is defined and no
> demultiplexing is done using init_setup callback. As other
> drivers call ide_setup_pci_device() directly in such
> 03_ide_cleanup_opti621.patch
>
> In drivers/ide/pci/opti612.[hc], init_setup_opt621() is
> declared, defined and referenced but never actullay used.
> Thie patch removes the function.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
> 02_ide_cleanup_it8172.patch
>
> In drivers/ide/pci/it8172.h, it8172_ratefilter() and
> init_setup_it8172() are declared and the latter is referenced
> in it8172_chipsets. Both functions are not defined or used
> anywhere. This patch removes the prototypes and
> 01_ide_remove_adma100.patch
>
> Removes drivers/ide/pci/adma100.[hc]. The driver isn't
> compilable (missing functions) and no Kconfig actually enables
> CONFIG_BLK_DEV_ADMA100.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Index:
Hello, B. Zolnierkiewicz.
These patches are various fixes/improvements to the ide driver. They
are against the 2.6 bk tree as of today (20050202).
01_ide_remove_adma100.patch
Removes drivers/ide/pci/adma100.[hc]. The driver isn't
compilable (missing functions) and no Kconfig
I've mentioned this problem before. It seemed to go away around the
2.6.8 timeframe, but when I started using 2.6.9, it came back. I'm
using 2.6.10, and it's still happening.
Basically, I get random poppling and crackling noises out of my
speakers. Sometimes it's silent, and sometimes, it
Hi everyone.
I'm pleased to announce that my new employer, Cyclades Corporation
(http://www.cyclades.com) has agreed to allow me to spend a significant
part of my paid hours each week working on issues related to the
Suspend2 patches and Power Management in general (in addition to my own
time
Hi.
On Wed, 2005-02-02 at 13:00, john stultz wrote:
> On Tue, 2005-02-01 at 17:48 -0800, Tim Bird wrote:
> > john stultz wrote:
> > > Interesting patch. Indeed, the trade off is just how quickly you want to
> > > boot vs how much drift you gain each suspend/resume cycle. Assuming all
> > > of the
Hi !
Is there any work in progress to get some unified error reporting (and
possibly recovery) API for PCI/X/e ?
On pSeries, we have this "EEH" mecanism that allows us, even with
old-style PCI, to get error notification, but also to recover by doing
slot reset and that sort of stuff.
PCI
On Tue, Feb 01, 2005 at 04:15:36PM -0500, Mike Waychison wrote:
> No. I want to allow the mount. However, if there are several shared
> '/home' (through CLONE_NS or mount --bind), there remains the following
> two key problems:
>
> - - How do you expire the mounts and umount them? (undefined
On Tue, 2005-02-01 at 17:48 -0800, Tim Bird wrote:
> john stultz wrote:
> > Interesting patch. Indeed, the trade off is just how quickly you want to
> > boot vs how much drift you gain each suspend/resume cycle. Assuming all
> > of the clocks are good, your patch could introduce up to 2 seconds of
Hi, Andrew
Could you please check it ? I have worked out my little patch to fix
it. But not any feedback. Is it ok in your machine which is not-SMP?
Regards
--
Zhonglin Zhang <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
David Gibson wrote:
Following are a bunch of patches which make a few more steps towards
the long overdue merge of the CVS orinoco driver into mainline. These
do make behavioural changes to the driver, but they should all be
trivial and largely cosmetic.
OK, the changes look good, but I was
john stultz wrote:
> Interesting patch. Indeed, the trade off is just how quickly you want to
> boot vs how much drift you gain each suspend/resume cycle. Assuming all
> of the clocks are good, your patch could introduce up to 2 seconds of
> drift each suspend/resume cycle.
If we're not writing
On Tue, 2005-02-01 at 17:20 -0800, Christoph Lameter wrote:
> On Wed, 2 Feb 2005, Nick Piggin wrote:
>
> > > The unmapping in rmap.c would change the pte. This would be discovered
> > > after acquiring the spinlock later in do_wp_page. Which would then lead to
> > > the operation being abandoned.
On Tue, Feb 01, 2005 at 06:37:54PM -0500, J. Bruce Fields wrote:
> I think the question you meant to ask was what would happen if you
> mounted something on /tmp/mnt2/a/b (the slave copy) and then mounted
> something else on /tmp/mnt1/a/b. In that case there's two places where
> the propagated
Andreas Gruenbacher <[EMAIL PROTECTED]> said:
[...]
> Yes, because a custom swap routine isn't very useful generally. It's
> over-engineered IMHO.
It shouldn't swap, but juggle elements around like so:
t --->+
^ |
| v
x <-- x <-- x
On Wed, Feb 02, 2005 at 03:15:14AM +0200, Alexey Dobriyan wrote:
> P. S.: struct mv64xxx_i2c_data revisited...
>
> > + uintstate;
> > + ulong reg_base_p;
>
> Silly request, but... Maybe this should be changed to plain old "unsigned int"
> and "unsigned
On Wed, 2 Feb 2005, Nick Piggin wrote:
> > The unmapping in rmap.c would change the pte. This would be discovered
> > after acquiring the spinlock later in do_wp_page. Which would then lead to
> > the operation being abandoned.
> Oh yes, but suppose your page_cache_get is happening at the same
Hi,
I had a lot of problems with the transport stream input on the
SAA7134. Even the slighest bit of other system activity caused data
corruption. This patch corrects the switching of the two DMA
buffers.
Without the patch, the driver updates the buffer that is just about to
be used by the chip.
On Feb 01, 2005, at 10:24, Bill Davidsen wrote:
As a general thing I think DEPRECIATED would be useful for the case
where there is a newer functional driver.
I guess a "DEPRECIATED" driver is one where the code is written off
linearly
over a 7 year period. ;) I assume you mean DEPRECATED, not
On Tue, 2005-02-01 at 15:20 -0500, Lee Revell wrote:
> I was wondering how Windows handles high res timers, if at all. The
> reason I ask is because I have been reverse engineering a Windows ASIO
> driver, and I find that if the latency is set below about 5ms, by
By default, Windows
On Tue, Feb 01, 2005 at 02:56:25PM -0800, Greg KH wrote:
> On Sun, Jan 23, 2005 at 05:19:11AM +0100, Kay Sievers wrote:
> > This patch sequence moves the creation of the sysfs "dev" file of the class
> > devices into the driver core. The struct class_device contains a dev_t
> > value now. If set,
On Tue, 2005-02-01 at 11:01 -0800, Christoph Lameter wrote:
> On Tue, 1 Feb 2005, Nick Piggin wrote:
> > A per-pte lock is sufficient for this case, of course, which is why the
> > pte-locked system is completely free of the page table lock.
>
> Introducing pte locking would allow us to go
Hi.
On Wed, 2005-02-02 at 11:27, john stultz wrote:
> > We call the suspend and resume methods because the suspend is supposed
> > to achieve atomicity, and the resume is necessary for us to be able to
> > write the image. (Remember that these calls are invoked as part of the
> > drivers_suspend
On Tue, 1 Feb 2005, Christoph Lameter wrote:
> On Tue, 1 Feb 2005, Mel Gorman wrote:
>
> > > Would it not be better to zero the global 2^MAX_ORDER pages by the scrub
> > > daemon and have a global zeroed page list? That way you may avoid zeroing
> > > when splitting pages?
> > >
> >
> > Maybe,
On Wed, 2005-02-02 at 11:04 +1100, Nigel Cunningham wrote:
> Hi.
>
> On Wed, 2005-02-02 at 10:32, john stultz wrote:
> > interesting, I wasn't aware of the suspend/copy/resume process that
> > occurs for suspend-to-disk. The thing I don't quite get is why are the
> > resume methods called before
On Tue, 2005-02-01 at 15:53 -0800, Tim Bird wrote:
> john stultz wrote:
> > I believe you're right. Although we don't call read_persistent_clock()
> > very frequently, nor do we call it in ways we don't already call
> > get_cmos_time(). So I'm not sure exactly what the concern is.
>
> Sorry - I
On Tue, Feb 01, 2005 at 10:44:39AM +0100, Peter Busser wrote:
> Again, this is a *simulation* of the way real-life applications could
> interact
> with the underlying system. Again people complained that the results shown
> were not accurate. And that has been fixed.
>
> I am well aware of
Hi!
> >Now, if you want to help, just convert some drivers... To quickly
> >break compilation in case of bad types, following patch can be used
> >(against 2.6.11-rc2-mm1), it actually switches pm_message_t to
> >typedef.
> >
> >I'm looking forward to the patches, (please help),
>
> I just had a
Hi Pavel,
Pavel Machek wrote:
Now, if you want to help, just convert some drivers... To quickly
break compilation in case of bad types, following patch can be used
(against 2.6.11-rc2-mm1), it actually switches pm_message_t to
typedef.
I'm looking forward to the patches, (please help),
I just had
On Tue, 1 Feb 2005, Mel Gorman wrote:
> > Would it not be better to zero the global 2^MAX_ORDER pages by the scrub
> > daemon and have a global zeroed page list? That way you may avoid zeroing
> > when splitting pages?
> >
>
> Maybe, but right now when there are no 2^MAX_ORDER pages, the scrub
Hi.
On Wed, 2005-02-02 at 10:32, john stultz wrote:
> On Wed, 2005-02-02 at 10:14 +1100, Nigel Cunningham wrote:
> > Hi John and Tim.
> >
> > On Wed, 2005-02-02 at 09:48, john stultz wrote:
> > > > I didn't scan for all uses of read_persistent_clock, but
> > > > in my experience get_cmos_time()
john stultz wrote:
> I believe you're right. Although we don't call read_persistent_clock()
> very frequently, nor do we call it in ways we don't already call
> get_cmos_time(). So I'm not sure exactly what the concern is.
Sorry - I should have given more context. I am worried about
suspend and
This patch adds a show_options function to the proc filesystem.
diff -pur l2/fs/proc/inode.c l3/fs/proc/inode.c
--- l2/fs/proc/inode.c 2005-02-01 04:51:23.0 +0100
+++ l3/fs/proc/inode.c 2005-02-01 04:51:07.0 +0100
@@ -16,6 +16,7 @@
#include
#include
#include
+#include
This patch adds the umask option to the proc filesystem. It's
essentially unchanged from the previous version, except that the mount
option has to be specified as a kernel parameter now. This way we avoid
dealing with pre-existing inodes.
The umask can be used to restrict the permissions of
Hello,
while trying to add a umask option to the proc filesystem I stumbled
over a somewhat related problem: the existing mount options uid and
gid were non-functional. The patch below is an attempt to fix them
and prepares the ground for my evil umask plans. :)
The first half of the reason why
On Tue, 1 Feb 2005, Adrian Bunk wrote:
> On Tue, Feb 01, 2005 at 10:24:56AM -0500, Bill Davidsen wrote:
> > Adrian Bunk wrote:
> > >On Sat, Jan 29, 2005 at 06:22:55PM +0100, Jean Delvare wrote:
> > >
> > >>Hi Adrian,
> > >>
> > >>
> > >>>The mcd driver drives only very old hardware (some single
On Tue, 2005-02-01 at 21:44 +0100, Ingo Molnar wrote:
> * Lee Revell <[EMAIL PROTECTED]> wrote:
>
> > OK. So for application triggered tracing you need LATENCY_TRACING
> > enabled, as described here:
> >
> > http://lkml.org/lkml/2004/10/29/312
>
> correct, that too should still work fine -
* Lee Revell <[EMAIL PROTECTED]> [050201 12:20]:
> On Thu, 2005-01-27 at 13:29 -0800, Tony Lindgren wrote:
> > Hi all,
> >
> > Thanks for all the comments, here's an updated version of the dynamic
> > tick patch.
>
> Hi,
>
> I was wondering how Windows handles high res timers, if at all. The
>
On Tue, Jan 25, 2005 at 02:02:43PM -0800, Ram wrote:
> oops. I had the following in mind.
>
> mount /tmp/mnt1
> ** mount --make-shared /tmp/mnt1 **
> mkdir -p /tmp/mnt1/a/b
> mount --rbind /tmp/mnt1 /tmp/mnt2
> mount --make-slave /tmp/mnt2
>
> In this case
On Tue, 2005-02-01 at 13:15, Mike Waychison wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> (Hmm.. something is up with my quoting again..)
>
> Ram wrote:
> > On Mon, 2005-01-31 at 23:02, Mike Waychison wrote:
> >
> > Ram wrote:
> >
> >>On Fri, 2005-01-28 at 14:31, Mike Waychison
Hi!
> > > > Move PM code from ide-cd.c and ide-disk.c to IDE core so:
> > > > * PM is supported for other ATAPI devices (floppy, tape)
> > > > * PM is supported even if specific driver is not loaded
> > >
> > > Why do you need to have state-machine? During suspend we are running
> > >
On Wed, 2005-02-02 at 10:14 +1100, Nigel Cunningham wrote:
> Hi John and Tim.
>
> On Wed, 2005-02-02 at 09:48, john stultz wrote:
> > > I didn't scan for all uses of read_persistent_clock, but
> > > in my experience get_cmos_time() has a latency of up to
> > > 1 second on x86 because it
1 - 100 of 595 matches
Mail list logo
