Chris Wright wrote:
* Zwane Mwaikambo ([EMAIL PROTECTED]) wrote:
On Wed, 10 Aug 2005 [EMAIL PROTECTED] wrote:
Add an accessor function for getting the per-CPU gdt. Callee must already
have the CPU.
This one seems superfluous to me, does accessing it indirectly generate
better code too?
On 8/11/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Magnus Damm <[EMAIL PROTECTED]> wrote:
> >
> > On 8/11/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > > Mel Gorman <[EMAIL PROTECTED]> wrote:
> > > > The majority of pages I am seeing no longer have page->mapping set. Does
> > > > this mean
* Zwane Mwaikambo ([EMAIL PROTECTED]) wrote:
> On Wed, 10 Aug 2005 [EMAIL PROTECTED] wrote:
>
> > Add an accessor function for getting the per-CPU gdt. Callee must already
> > have the CPU.
>
> This one seems superfluous to me, does accessing it indirectly generate
> better code too?
It's
On Wed, 10 Aug 2005 [EMAIL PROTECTED] wrote:
> Add an accessor function for getting the per-CPU gdt. Callee must already
> have the CPU.
This one seems superfluous to me, does accessing it indirectly generate
better code too?
> Patch-base: 2.6.13-rc5-mm1
> Patch-keys: i386 desc xen
>
I had this question. As per my understanding, in the
Linux system call implementation on x86 architecture
the call flows like this int 0x80 -> syscall ->
sys_call_vector(taken from the table)-> return from
interrupt service routine.
Now I had the doubt that if the the syscall
implementation is
On Wed, Aug 10, 2005 at 03:35:53PM -0700, Greg KH wrote:
> On Wed, Aug 10, 2005 at 03:36:36PM +0530, Maneesh Soni wrote:
> > On Wed, Aug 10, 2005 at 04:26:51PM +1000, Keith Owens wrote:
> > > FYI, the intermittent free after use in sysfs is still there in
> > > 2.6.13-rc6.
> > >
> >
> > The race
Dear all,
I am Linux driver programmer.
I have a FAT12 issue on my SD cards. I have got these addresses from the
fs-lists as the maintainer support mail IDs for FAT-FS.
I am using the 2.6.10 kernel, X86 like systems.
I am NOT able to mount the Camera formatted FAT12 filesystem on my linux
Xen uses lazy pinning of MM structures including the page table root and LDT,
which requires hooks at context creation and destruction time to maintain the
lazy list.
Patch-against: 2.6.13-rc5-mm1
Patch-keys: i386 mmu paravirt xen
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index:
Add hooks that the hypervisor can use to establish writable and non-writable
pages for LDT pages. I made these parallel the page flags as defined in
include/linux/page-flags.h, since the flag mechanism is very similar to the
hypercall page flagging, and extended easily later to include PT, PD,
By moving init_new_context and destroy_context inline into mmu_context.h,
we can avoid extra functions calls, which are only needed for the unlikely
case that the process context has an LDT to deal with.
Now the code in ldt.c is called only when actually dealing with LDT
creation or destruction.
Move base / limit accessors into desc.h, where they properly belong.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/system.h
===
---
Found some stray descriptor table accessors that had non-optimal assembler
constraints. Use "q" to get word, high and low byte access without forcing
a specific register constraint. Add desc as a memory output operand.
Also, get_base was completely unused. Deprecate it.
The function get_limit
Found yet another set of accessor functions for descriptors that really
belongs in desc.h - move it there.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/arch/i386/kernel/process.c
Use an early clobber on addr to avoid the extra rorl instruction at the
end of _set_tssldt_desc.
Also, get some C type checking on the descriptor struct here.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup optimize
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index:
Add some convenient descriptor access functions and move them all into desc.h
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/desc.h
===
Add an accessor function for getting the per-CPU gdt. Callee must already
have the CPU.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc xen
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/desc.h
for_each_cpu walks through all processors in cpu_possible_map, which is
defined as cpu_callout_map on i386 and isn't initialised until all
processors have been booted. This breaks things which do for_each_cpu
iterations early during boot. So, define cpu_possible_map as a bitmap with
NR_CPUS
The per-CPU initialization code is copying in bogus data into
thread->tls_array. Note that it copies _cpu(cpu_gdt_table, cpu),
not _cpu(cpu_gdt_table, cpu)[GDT_ENTRY_TLS_MIN). That is totally
broken and unnecessary. Make the initialization explicitly NULL.
Patch-base: 2.6.13-rc5-mm1
Add some convenient segment macros to the kernel. This makes the
rather obfuscated 'seg & 4' go away.
Patch-keys: i386 segment cleanup
Patch-base: 2.6.13-rc5-mm1
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/segment.h
Stop using extra underscores on asm and volatiles, that is just silly.
Also, make lgdt/lidt/sgdt/sldt explicitly "l".
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/mach-default/mach_desc.h
Xen requires error returns from the hypercall to update LDT entries,
and this generates completely equivalent code on native.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc ldt paravirt xen
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index:
Got too many complaints that this code is ugly. It is. Fix it.
Patch-base: 2.6.13-rc5-mm1
Patch-keys: i386 desc cleanup
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
Index: linux-2.6.13/include/asm-i386/mach-default/mach_desc.h
Magnus Damm <[EMAIL PROTECTED]> wrote:
>
> On 8/11/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > Mel Gorman <[EMAIL PROTECTED]> wrote:
> > > The majority of pages I am seeing no longer have page->mapping set. Does
> > > this mean they are in the process of being cleared up?
> >
> > They're
Hi,
On Wed, Aug 10, 2005 at 11:18:48PM +0300, Pekka J Enberg wrote:
> You, however, don't maintain the same level of data consistency when reads
> and writes are from other filesystems as they use ->nopage.
Mark Fasheh writes:
I'm not sure what you mean here...
Reading and writing from
On 10.08.2005 [23:19:01 -0400], Jeff Garzik wrote:
> [EMAIL PROTECTED] wrote:
> >From: Nishanth Aravamudan <[EMAIL PROTECTED]>
> >
> >
> >
> >Use set_current_state() instead of direct assignment of
> >current->state.
> >
> >Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
> >Signed-off-by:
Added ppc_sys device and system definitions for PowerQUICC II devices.
This will allow drivers for PQ2 to be proper platform device drivers.
Which can be shared on PQ3 processors with the same peripherals.
Signed-off-by: Matt McClintock <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL
[EMAIL PROTECTED] wrote:
From: Nishanth Aravamudan <[EMAIL PROTECTED]>
Use set_current_state() instead of direct assignment of
current->state.
Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
Signed-off-by: Maximilian Attems <[EMAIL PROTECTED]>
Signed-off-by: Domen Puncer <[EMAIL
On Wednesday 10 August 2005 05:21 pm, Protasevich, Natalie wrote:
> > > int gsi_irq_sharing(int gsi)
> > > {
> > > int i, irq, vector;
> > >
> > > BUG_ON(gsi >= NR_IRQ_VECTORS);
> > >
> > > if (platform_legacy_irq(gsi)) {
> > > gsi_2_irq[gsi] = gsi;
> > >
On Tue, 2005-08-09 at 19:03 -0700, Siddha, Suresh B wrote:
> On Wed, Aug 10, 2005 at 10:27:44AM +1000, Nick Piggin wrote:
> > Yeah this makes sense. Thanks.
> >
> > I think we'll only need your first line change to fix this, though.
> >
> > Your second change will break situations where a single
On 8/11/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Mel Gorman <[EMAIL PROTECTED]> wrote:
> > The majority of pages I am seeing no longer have page->mapping set. Does
> > this mean they are in the process of being cleared up?
>
> They're just anonymous pages, aren't they? But you said "pages
On Wed, 2005-08-10 at 19:39 -0700, john stultz wrote:
> Ah, I've got a patch on my laptop that takes that down to ~2% or less.
> I didn't include it in this patch set but I'll work to get it
> integrated before the next release. Sorry about that.
>
> If you have any suggestions for further
On Wed, 2005-08-10 at 22:32 -0400, Lee Revell wrote:
> On Wed, 2005-08-10 at 19:13 -0700, john stultz wrote:
> > All,
> > Here's the next rev in my rework of the current timekeeping subsystem.
> > No major changes, only some cleanups and further splitting the larger
> > patches into smaller
Hi,
This patch adds the return value check for sysdev suspend and does
restore in failure case. Send the patch to pm-list, but seems lost, so I
resend it.
Signed-off-by: Shaohua Li<[EMAIL PROTECTED]>
---
linux-2.6.13-rc3-root/drivers/base/sys.c | 110 +++
1 files
Apologies if these are known problems, but I don't recall seeing them
mentioned recently.
I'm running an athlon64 with 2.6.12.3, in the middle of rebuilding it
to run 64-bit. The main drive used to be in an i686 machine for
testing, and it got to a point where I wanted to repartition.
Under
On Wed, 2005-08-10 at 19:13 -0700, john stultz wrote:
> All,
> Here's the next rev in my rework of the current timekeeping subsystem.
> No major changes, only some cleanups and further splitting the larger
> patches into smaller ones.
Last I heard this made gettimeofday() 20% slower on x86.
Hi James,
Dropped back to 2.6.11.1 and it hung again. I was able to get the
drive back by power cycling it and then doing the scsiadd to drop and
re-add the drive. I then used the bacula 'btape' tool to run some
tests. It seems to be just fine with regular files, but when it hit
EOM, all hell
All,
This patch implements the time sources shared between i386 and x86-64
(acpi_pm, cyclone, hpet, pit, tsc and tsc-interp). The patch should
apply on top of the timeofday-arch-i386-part4 patch
The patch should be fairly straight forward, only adding the new
timesources.
thanks
All,
The conversion of i386 to use the generic timeofday subsystem has been
split into 6 parts. This patch, the final of four, removes the old
timers/timer_opts infrastructure.
It applies on top of my timeofday-arch-i386-part5 patch. This patch is
the last in the the timeofday-arch-i386
All,
The conversion of i386 to use the generic timekeeping subsystem has
been split into 6 parts. This patch, the fourth of six, renames some
ACPI PM variables.
It applies on top of my timeofday-arch-i386-part3 patch. This patch is
part the timeofday-arch-i386 patchset, so without the
All,
The conversion of i386 to use the generic timekeeping subsystem has
been split into 6 parts. This patch, the fifth of six, converts the i386
arch to use the generic timekeeping subsystem.
It applies on top of my timeofday-arch-i386-part4 patch. This patch is
part the
All,
The conversion of i386 to use the generic timekeeping subsystem has
been split into 6 parts. This patch, the second of six, is a cleanup
patch for the i386 arch in preperation of moving the the generic
timekeping infrastructure. It moves some code from timer_tsc.c to a new
tsc.c file.
All,
The conversion of i386 to use the generic timekeeping subsystem has
been split into 6 parts. This patch, the third of six, reworks some of
the code in the new tsc.c file, adding some new interfaces and hooks to
use these new interfaces appropriately.
It applies on top of my
All,
The conversion of i386 to use the generic timekeeping subsystem has
been split into 6 parts. This patch, the first of six, is just a simple
cleanup for the i386 arch in preperation of moving the the generic
timekeeping infrastructure. It simply moves some code from timer_pit.c
to
Just to make sure to avoid all confusion. The title of this thread should
be
"[PATCH] Fix ide-disk.c oops caused by hwif->pci_dev == NULL"
And this is the patch that was acknowledged by Andrew and that fixes the
issue AFAIK. This patch needs to be included in 2.6.13. Lets make sure
that we
All,
This patch implements the architecture independent portion of the
generic time of day subsystem. Included below is timeofday.c (which
includes all the time of day management and accessor functions), and
minimal hooks into arch independent code.
This patch applies on top of my timesource
All,
This patch introduces the timesource management infrastructure. A
timesource is a driver-like architecture generic abstraction of a
freerunning counter. This patch defines the timesource structure, and
provides management code for registering, selecting, accessing and
scaling
All,
Here's the next rev in my rework of the current timekeeping subsystem.
No major changes, only some cleanups and further splitting the larger
patches into smaller ones.
The goal of this patch set is to provide a simplified and streamlined
common timekeeping infrastructure that
Comments below ...
On Thu, 2005-08-11 at 09:43 +, yangyi wrote:
> +#ifndef CONFIG_CRITICAL_LATENCY_HIST
> if (!report_latency(delta))
> goto out;
> +#endif
Why ? This combined with the hunk below is just preempt_threshold ..
Just use preempt_threshold instead of all the
On Thu, 2005-08-04 at 15:52 +0200, Ingo Molnar wrote:
> would be nice to clean up the impact of the latency-histogram code some
> more though: e.g. the #ifdef jungle check_critical_timing() is
> disgusting. Could be cleaned up by always recording the latency_type
> being currently traced into
Hi, Ingo
According to your suggestion, I check your cleanup and correct some errors and
modify latency type decision.
This patch corrects some latency histogram configration options name, adds
a field to cpu_trace struct, removes that ugly latenct type decision statement
block, adds a
All,
This patch replaces two global variables with better named static local
variables. Additionally it adds my copyright.
Any comments or feedback would be greatly appreciated.
thanks
-john
linux-2.6.13-rc6_timeofday-ntp-part13_B5.patch
diff
All,
This patch simplifies and cleans up the adjtime code in ntp_advance and
corrects a comment.
Any comments or feedback would be greatly appreciated.
thanks
-john
linux-2.6.13-rc6_timeofday-ntp-part12_B5.patch
diff --git a/kernel/ntp.c
All,
This patch introduces variables to keep track of the different NTP
adjustment values in PPM units. It also introduces the
ntp_get_ppm_adjustment() interface which returns shifted PPM units. The
patch also changes the ppc64 ppc_adjtimex() function to use
ntp_get_ppm_adjustment().
On Wed, Aug 10, 2005 at 06:15:56PM +0100, Daniel Drake wrote:
> As for captive, I don't think its worth the effort. It has severe memory
> problems and Linux-NTFS development is going quite fast anyway.
I haven't seen any real changes in NTFS support in the kernel since
the mid-2.5 series.
All
This patch changes the NTP variable names from time_* to ntp_* further
clarifing their use.
Any comments or feedback would be greatly appreciated.
thanks
-john
linux-2.6.13-rc6_timeofday-ntp-part9_B5.patch
diff --git
All,
This patch introduces the ntp_lock which replaces the xtime_lock for
serialization in the NTP subsystem. This further isolates the NTP
subsystem from the time subsystem.
Any comments or feedback would be greatly appreciated.
thanks
-john
All
This patch removes the second_overflow() logic integrating it into the
ntp_advance() function. This provides a single interface to advance the
internal NTP state machine.
Any comments or feedback would be greatly appreciated.
thanks
-john
All,
This patch breaks up the complex nesting of code in ntp_adjtimex() by
creating a ntp_hardupdate() function and simplifying some of the logic.
This also mimics the documented NTP spec somewhat better.
Any comments or feedback would be greatly appreciated.
thanks
-john
All,
Signed shifting must be done carefully, and the ntp code has quite a
number of conditionals to do the signed shifting. This patch makes use
of the shiftR() macro introduced in a previous patch to simplify a bit
of logic.
Any comments or feedback would be greatly appreciated.
thanks
All,
Since the NTP PPS code required an out of tree patch which I don't
believe there is a 2.6 version of, this patch removes the unused PPS
logic in the kernel.
Any comments or feedback would be greatly appreciated.
thanks
-john
linux-2.6.13-rc6_timeofday-ntp-part3_B5.patch
> "Trond" == Trond Myklebust <[EMAIL PROTECTED]> writes:
Trond> to den 11.08.2005 Klokka 09:48 (+1000) skreiv Peter Chubb:
>> Hi, The LTP test fcntl23 is failing. It does, in essence, fd =
>> open(xxx, O_RDWR|O_CREAT, 0777); if (fcntl(fd, F_SETLEASE, F_RDLCK)
>> == -1) fail;
>>
>> fcntl
All
Currently ntp_adjtimex() checks the validity of a few arguments values
then takes the xtime_lock then checks the validity of more arguements
while it parses them. This separates the logic so we check the validity
of all arguements before aquiring the xtime lock. This greatly improves
All,
This patch breaks the leapsecond processing logic into its own
function. By making the NTP code avoid making any direct changes to
time, instead allowing the time code to use NTP to decide when to change
time, we better isolate the NTP subsystem.
Any comments or feedback would be
All,
This patch moves the generic NTP code from time.c and timer.c into
ntp.c. It makes most of the NTP variables static providing more
understandable interfaces like ntp_synced() and ntp_clear().
Since some of the newly made static variables are used in arch generic
code, this
All,
This patch converts all of arch specific code to use the new ntp_synced
() and ntp_clear() interfaces. This patch is required for the patch 1 of
the series to build.
Any comments or feedback would be greatly appreciated.
thanks
-john
linux-2.6.13-rc6_timeofday-ntp-part2_B5.patch
All,
The goal of this patch set is to isolate the in kernel NTP state
machine in the hope of simplifying the current timekeeping code and
allowing for optional future changes in the timekeeping subsystem.
I've tried to address some of the complexity concerns for systems that
do not have a
If you want an expediant answer to a networking related
kernel question, you may wish to post this to
netdev@vger.kernel.org which (unlike here) is where the
kernel networking developers are subscribed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
to den 11.08.2005 Klokka 09:48 (+1000) skreiv Peter Chubb:
> Hi,
> The LTP test fcntl23 is failing. It does, in essence,
> fd = open(xxx, O_RDWR|O_CREAT, 0777);
> if (fcntl(fd, F_SETLEASE, F_RDLCK) == -1)
> fail;
>
> fcntl always returns EAGAIN here. The manual page
On Wed, Aug 10, 2005 at 05:43:23PM -0700, yhlu wrote:
> Yes, I mean more aggressive
>
> static void __init smp_init(void)
> {
> unsigned int i;
>
> /* FIXME: This should be done in userspace --RR */
> for_each_present_cpu(i) {
> if (num_online_cpus() >=
In a conversation the other yesterday about web servers, this came up
in conversation by another much more informed than I. I'm not sure if
the information is up to date to current kernel builds, so I pose the
question here: Does the linux kernel block on SO_LINGER?
Here is paragraph in the other
Yes, I mean more aggressive
static void __init smp_init(void)
{
unsigned int i;
/* FIXME: This should be done in userspace --RR */
for_each_present_cpu(i) {
if (num_online_cpus() >= max_cpus)
break;
if
I just noticed that the Ubuntu setup says "GSI 20(level,low) -> IRQ 20"
whereas I remember my built kernels saying "No GSI.. IRQ 11". I'll
investigate what that means and how to enable it. Pointers appreciated.
sdw
Stephen D. Williams wrote:
I have been working for days to get a
I have been working for days to get a recent kernel to work with these
small-format UP Celeron 2Ghz (running at 1.33Ghz) motherboards that I am
planning to use as thin clients. I'm doing a PXE boot, loading kernels,
and trying to get networking to come up.
I eventually realized that the
On Wed, Aug 10, 2005 at 05:23:31PM -0700, yhlu wrote:
> I wonder if you can make the bsp can start the APs callin in the same
> time, and make it asynchronous, So you make spare 2s or more.
The setting of cpu_callin_map in the AP could be moved earlier yes.
But it's not entirely trivial because
Daniel Petrini wrote:
I'd like to have an idea of how the powerop would evolve to address:
a) exporting all operating points to sysfs - that would be useful for
a policy manager in user space, or the user policy will already be
aware of the ops?
For different usage models I'd expect to see
I wonder if you can make the bsp can start the APs callin in the same
time, and make it asynchronous, So you make spare 2s or more.
YH
On 8/10/05, yhlu <[EMAIL PROTECTED]> wrote:
> In LinuxBIOS, we could init_ecc asynchronous and the time reduced from
> 8x to 2.1x for 8 ways system. 1x mean 5s
> > int gsi_irq_sharing(int gsi)
> > {
> > int i, irq, vector;
> >
> > BUG_ON(gsi >= NR_IRQ_VECTORS);
> >
> > if (platform_legacy_irq(gsi)) {
> > gsi_2_irq[gsi] = gsi;
> > return gsi;
> > }
> >
> > if (gsi_2_irq[gsi] != 0xFF)
On Wed, 10 Aug 2005 09:59:01 -0700 "Luck, Tony" <[EMAIL PROTECTED]>
wrote:
>
> >Some architectures have a too different ptrace so we have to exclude
> >them: alpha, ia64, m32r, parisc, sparc, sparc64. They continue to
> >keep their implementations.
>
> So it should be no surprise that this patch
In LinuxBIOS, we could init_ecc asynchronous and the time reduced from
8x to 2.1x for 8 ways system. 1x mean 5s for 4G in one cpu. If 16G
will take 20s.
for TSC_SYNC asynchronous maybe you can get back 0.1s...
YH
On 8/10/05, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > So my patch still can be
On Wed, 10 Aug 2005, Marcelo Tosatti wrote:
> First of all, this is very nice! The code is amazingly easy to read.
Thank you.
> You change the rate of active list scanning, which I suppose won't
> change the current reclaiming behaviour much (at least not on the
> "stress system to death" tests
> So my patch still can be used with Eric's, It just serialize the
> TSC_SYNC between cpu.
>
> I wonder it you can refine to make TSC_SYNC serialize that beteen CPU.
> That will make
> CPU X:synchronized TSC ...
> in fixed postion and timming.
Why would we want that?
Boot time is critical so
I'm for its removal. As for the gcc project "losing its way" consider
that 3.4 has quite matured and also has much smaller binary size from
3.3. 4.0 however is still too early in its development to come close
to surpassing 3.4.
With all the changes and deprications it seems pointless to have to
David Madore wrote:
Hi. I apologize for what is surely a stupid question: I understand
that ACPI should be able to tell me what my CPU's temperature is (I
have a sever overheating problem and I am trying to solve it by
underclocking somewhat, but I need to be able to read the temperature
to do
Comments below.
On Wednesday 10 August 2005 02:03 pm, Protasevich, Natalie wrote:
> > Due to some device driver issues, I built this iteration of
> > the patch vs. 2.6.12.3.
> >
> > (Sorry about the attachment, but KMail is still word wrapping
> > inserted files.)
> >
> > Background:
> >
> >
Andi Kleen wrote:
On Wed, Aug 10, 2005 at 04:14:19PM -0700, Mike Waychison wrote:
YhLu wrote:
andi,
please refer the patch, it will move cpu_set(, cpu_callin_map) from
smi_callin to start_secondary.
This patch fixes an apparent race / lockup on our 2-way dual cores (when
applied against
Hi,
The LTP test fcntl23 is failing. It does, in essence,
fd = open(xxx, O_RDWR|O_CREAT, 0777);
if (fcntl(fd, F_SETLEASE, F_RDLCK) == -1)
fail;
fcntl always returns EAGAIN here. The manual page says that a read
lease causes notification when `another
On Wed, 10 Aug 2005, Alan Cox wrote:
> On Maw, 2005-08-09 at 19:59 -0700, Christoph Lameter wrote:
> > Yes you are right there is one additional place where pcibus_to_node is
> > used with the hwif that we did not cover. This better go into 2.6.13.
>
> drive->hwif is not permitted to be NULL.
On Thu, Aug 11, 2005 at 08:23:53AM +1000, Daniel Phillips wrote:
> Note: I have not fully audited the NFS-related colliding use of page flags
> bit
> 8, to verify that it really does not escape into VFS or MM from NFS, in fact
> I have misgivings about end_page_fs_misc which uses this flag but
andi,
you can see the difference with the patch
Booting processor 1/1 rip 6000 rsp 810181c61f58
Initializing CPU#1
masked ExtINT on CPU#1
Calibrating delay using timer specific routine.. 4000.31 BogoMIPS (lpj=8000624)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2
Dave Jones wrote:
I'm glad I'm not the only one who feels he's too dumb to see
the advantages of this. The added complexity to expose something
that in all cases, we actually don't want to expose seems a little
pointless to me.
For example, most of the x86 drivers, if you set a speed, and then
On Thu, Aug 11, 2005 at 12:06:16AM +0200, DervishD wrote:
> Hi Tomasz :)
>
> * Tomasz Torcz <[EMAIL PROTECTED]> dixit:
> > On Wed, Aug 10, 2005 at 09:22:43PM +0200, DervishD wrote:
> > > The problem is that if I plug my USB memory, unplug it and plug
> > > my MP3 player, it gets /dev/sdb
Mike Waychison wrote:
This patch fixes an apparent race / lockup on our 2-way dual cores (when
applied against 2.6.12.3). The machine was locking up after
"Initializing CPU#2".
the better ways is to use the patch from Eric that Andi posted to stable
yesterday:
Hi Rik,
First of all, this is very nice! The code is amazingly easy to read.
Now the usual ranting:
You change the rate of active list scanning, which I suppose won't
change the current reclaiming behaviour much (at least not on the
"stress system to death" tests which most folks use to test
On Wed, Aug 10, 2005 at 04:14:19PM -0700, Mike Waychison wrote:
> YhLu wrote:
> >andi,
> >
> >please refer the patch, it will move cpu_set(, cpu_callin_map) from
> >smi_callin to start_secondary.
>
>
> This patch fixes an apparent race / lockup on our 2-way dual cores (when
> applied against
to den 11.08.2005 Klokka 08:57 (+1000) skreiv Daniel Phillips:
> > What "NFS-related colliding use of page flags bit 8"?
>
> As explained to me:
>
> http://marc.theaimsgroup.com/?l=linux-kernel=112368417412580=2
Oh. You are talking about CacheFS? That hasn't been declared "ready to
merge" yet.
On Thursday 11 August 2005 00:27, David Howells wrote:
> What happens is this:
>
> (1) readpage() is issued against NFS (for example).
>
> (2) NFS consults the local cache, and finds the page isn't available
> there.
>
> (3) NFS reads the page from the server.
>
> (4) NFS sets PG_fs_misc and
YhLu wrote:
andi,
please refer the patch, it will move cpu_set(, cpu_callin_map) from
smi_callin to start_secondary.
This patch fixes an apparent race / lockup on our 2-way dual cores (when
applied against 2.6.12.3). The machine was locking up after
"Initializing CPU#2".
Mike Waychison
On 8/10/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello.
> My machine (i386, acer 1350) stops to work with 2.6.13-rc6. it works with
> "acpi=off". the abend seems to be a total deadlock. no system request keys
> works. no oops with log level 9.
> could someone please have a look at
Jean Delvare wrote:
Could you try running "i2cdump 0 0x50" and "i2cdump 0 0x50 i" (with the
patch still applied), and compare both the outputs and the time each
command takes? You should see similar outputs, but the second command
should be magnitudes faster. This would confirm that the I2C
Sorry, I actually figured it out.
I had the adaptec i2o driver built in the kernel along with the i2o
items in the main driver list and they were conflicting with each
other. I removed the i2o items from the main list and now everything
works good.
Thanks,
Jon
Martin J. Bligh wrote:
>--On
1 - 100 of 652 matches
Mail list logo
