On Fri, 9 Sep 2005, Keith Owens wrote:
> The new ia64 MCA/INIT handlers[1] (think of them as super NMI) run on
> separate stacks. 99% of the changes for these new handlers is ia64
> only code, however they need a couple of scheduler hooks to support
> these extra stacks. The complete patch set w
>> >Index: linux/arch/x86_64/kernel/traps.c
>>
>===
>> >--- linux.orig/arch/x86_64/kernel/traps.c
>> >+++ linux/arch/x86_64/kernel/traps.c
>> >@@ -931,7 +931,7 @@ void __init trap_init(void)
>> >set_system_gate(IA32_SYSCALL_VECTOR,
> ??? This is what the code doing the setup does. But the question was -
> what do you need the IDT entry for?
Without an IDT entry you cannot receive it?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Linux Kernel Mailing List wrote:
>
> tree 090c471fdb44d8fe88c52e95be0e8e43e31fcd5a
> parent d7271b14b2e9e5905aba0fbf5c4dc4f8980c0cb2
> author Zwane Mwaikambo <[EMAIL PROTECTED]> Sun, 04 Sep 2005 05:56:51 -0700
> committer Linus Torvalds <[EMAIL PROTECTED]> Mon, 05 Sep 2005 14:06:13 -0700
>
> [PAT
John W. Linville wrote:
Any chance you could re-diff this to apply on top of the patch posted
earlier today by Neil Horman?
Sure, but his patch didn't apply to -git8.
If Neil would please resend, then I can diff against that.
-Tommy
-
To unsubscribe from this list: send the line "unsubscribe
Hi Petr,
Petr Vandrovec schrieb:
> Enable displaying of connection watchdog logouts on the server. Do not
> use 'intr' mount option. Do not send KILL signal to the connection
> which is waiting for reply from server. If you are not sure that your
> network infrastructure is fine, use 'hard' mou
On Fri, 9 Sep 2005, Andrew Morton wrote:
> > static void __init MP_processor_info (struct mpc_config_processor *m)
> > {
> > - int ver, apicid;
> > + int ver, apicid, cpu, found_bsp = 0;
> > physid_mask_t tmp;
> >
> > if (!(m->mpc_cpuflag & CPU_ENABLED))
> > @@ -181,6 +181,7 @@
Tommy Christensen <[EMAIL PROTECTED]> wrote:
>
> John W. Linville wrote:
> > Any chance you could re-diff this to apply on top of the patch posted
> > earlier today by Neil Horman?
>
> Sure, but his patch didn't apply to -git8.
>
> If Neil would please resend, then I can diff against that.
>
Is
--- Alex Riesen <[EMAIL PROTECTED]> wrote:
> On 9/8/05, Ahmad Reza Cheraghi
> <[EMAIL PROTECTED]> wrote:
> > I made this Framework to generate a .config based
> on a
> > Target-System. Right-now it works on my Laptop
> Acer
>
> how about teaching it to generate .config using just
> sysfs and ls
On 9/9/05, Paul Jackson <[EMAIL PROTECTED]> wrote:
> magnus wrote:
> > Maybe it is possible to have an hierarchical model and keep the
> > framework simple and easy to understand while providing guarantees,
>
> Dinakar's patches to use cpu_exclusive cpusets to define dynamic
> sched domains accomp
Hi Andrew,
I think the following isn't on purpose but the IBM Thinkpad acpi
extras default to y in Kconfig. The patch below fixes it:
Signed-off-by: <[EMAIL PROTECTED]>
--- drivers/acpi/Kconfig.orig 2005-09-09 09:46:26.0 +0200
+++ drivers/acpi/Kconfig2005-09-09 09:46:
(Note: Patch also attached because the inline version is certain to get
line wrapped.)
Make the double fault handler use CPU-specific stacks, add some
abstraction
to simplify future change of other exception handlers to go through
task
gates. Change the pointer validity checks in the double fault
>>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 09:14:07 >>>
>> ??? This is what the code doing the setup does. But the question was
-
>> what do you need the IDT entry for?
>
>Without an IDT entry you cannot receive it?
But that's the point - if it's delivered as an NMI, it'll arrive
through vector
On Friday 09 September 2005 09:57, Jan Beulich wrote:
> >>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 09:14:07 >>>
> >>
> >> ??? This is what the code doing the setup does. But the question was
>
> -
>
> >> what do you need the IDT entry for?
> >
> >Without an IDT entry you cannot receive it?
>
> But
On Thursday 08 September 2005 18:38, Tom Rini wrote:
> This adds a call to notify_die() in the "no context" portion of
> do_page_fault() as someone on the chain might care and want to do a fixup.
>
> ---
>
> linux-2.6.13-trini/arch/x86_64/mm/fault.c |4
> 1 files changed, 4 insertions(+)
Brian wrote:
> The right fix is to get rid of that god-awful circular dependency on
> offset.h
Just try making such a patch. I double triple dare you.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL
On Thursday 08 September 2005 18:39, Tom Rini wrote:
> The existing hook from KDB in the IPI code is really just a hook for the
> NMI vector. We rename the vector thusly and then it's up to the
> debugger to handle things from do_default_nmi().
Jan Beulich pointed out some problems with this:
-
On Thursday 08 September 2005 18:37, Tom Rini wrote:
> It can be handy in some situations to have run trap_init() sooner than the
> generic code does. In order to do this on x86_64 we need to add a custom
> early_setup_per_cpu_areas() call as well.
Queued, thanks.
-Andi
-
To unsubscribe from thi
Hi everyone. I'm seeing something very Odd with 2.6.11 / 2.6.12 and 2.6.13, it has me stumped so I want to describe my
problem here and hopefully some kind soul can verify that what I am seeing is a Feature and NotABug :-)
It it's a Feature, then I'll find some way to work around it, but it seem
On Fri, 9 Sep 2005, Anthony Wesley wrote:
Hi everyone. I'm seeing something very Odd with 2.6.11 / 2.6.12 and 2.6.13,
it has me stumped so I want to describe my problem here and hopefully some
kind soul can verify that what I am seeing is a Feature and NotABug :-)
It it's a Feature, then I'll
Mike Houston wrote:
> On Thu, 08 Sep 2005 21:27:42 +0200
> Andreas Baer <[EMAIL PROTECTED]> wrote:
>
>
>
>>I think it's 2TB for the file size and 2e73 for the file system, but
>>I don't understand the second reference and the part about the
>>CONIFG_LBD. What is exactly the CONFIG_LBD option?
On Thursday 08 September 2005 17:52, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Being the foundation for reliable stack unwinding, this fixes CFI
> unwind
> annotations in many low-level x86_64 routines, plus a config option
> (
Magnus wrote:
> Non-overlapping subsets of cpu or memory nodes basically mean that
> children of a cpuset only clear bits in the bitmap, never sets them.
X is a subset of Y if every element of X is also in Y.
My phrase "a subset of the CPUs" really just meant "some set of CPUs"
on the system. A
On Thursday 08 September 2005 18:11, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Don't call nmi_watchdog_tick() when this isn't enabled.
Hmm, I think i will concur with Zwane's objection to this for now.
-Andi
-
To unsubscribe
The following 6 patches cleanup the jbd code and kill about 200 lines.
First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2.
The rest of them can apply to 2.6.13-mm2.
fs/jbd/checkpoint.c | 179 +++
fs/jbd/commit.c | 101 ++
>The UNWIND_INFO part has still some problems - in particular it is
lying
>on all other architectures which don't check it yet. I made it
dependent
>on X86_64 right now.
I don't think so. First, the i386 patch also adds the same (as I
indicated), and second this controls also the
-fasynchronous-ex
use struct hlist_head and hlist_node for the revoke tables.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
revoke.c | 56 ++--
1 files changed, 26 insertions(+), 30 deletions(-)
diff -Nurp 2.6.13-mm1.old/fs/jbd/revoke.c 2.6.13-mm1/fs/j
remove duplicated debug print
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
commit.c |2 --
1 files changed, 2 deletions(-)
--- 2.6-mm/fs/jbd/commit.c.orig 2005-09-02 00:53:49.0 +0900
+++ 2.6-mm/fs/jbd/commit.c 2005-09-02 00:54:11.0 +0900
@@ -425,8 +425,6 @@ writ
On Friday 09 September 2005 10:48, Jan Beulich wrote:
> >The UNWIND_INFO part has still some problems - in particular it is
>
> lying
>
> >on all other architectures which don't check it yet. I made it
>
> dependent
>
> >on X86_64 right now.
>
> I don't think so. First, the i386 patch also adds the
On Thursday 08 September 2005 18:07, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Declare NMI_VECTOR and handle it in the IPI sending code.
I would apply it now, but the attachment is empty. Can you resend?
-Andi
-
To unsubscrib
use struct list_head for doubly-linked list of buffers on a transaction's
data, metadata or forget queue.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
fs/jbd/checkpoint.c | 12 ++--
fs/jbd/commit.c | 79 --
fs/jbd/journal.c
use loop counter for initializing/destroying a pair of the revoke tables.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
revoke.c | 116 ++-
1 files changed, 42 insertions(+), 74 deletions(-)
diff -X 2.6.13-mm1/Documentation/don
On Thursday 08 September 2005 18:09, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Rather than blindly re-enabling interrupts in oops_end(), save their
> state
> in oope_begin() and then restore that state.
Thanks queued. Please
use struct list_head for a linked circular list of all transactions
waiting for checkpointing on a journal control structure.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
fs/jbd/checkpoint.c | 48
fs/jbd/commit.c | 16 ++-
On Thursday 08 September 2005 18:06, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Set the stack pointer correctly in init_thread and init_tss.
Thanks applied.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe lin
On Thursday 08 September 2005 18:05, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Adjust, correct, and complete the HPET definitions for x86-64.
Thanks applied.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe l
On Thursday 08 September 2005 18:04, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Allow building the x86-64 kernels with frame pointers if so needed.
This doesn't work because you would need to pass -fno-omit-frame-pointer
somewh
On Thursday 08 September 2005 18:03, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> While only cosmetic for x86-64, this adjusts the cmpxchg code
> appearantly
> inherited from i386 to use more generic constraints.
Attachment is em
>>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 10:43:01 >>>
>On Thursday 08 September 2005 18:11, Jan Beulich wrote:
>> (Note: Patch also attached because the inline version is certain to
get
>> line wrapped.)
>>
>> Don't call nmi_watchdog_tick() when this isn't enabled.
>
>Hmm, I think i will concur
use struct list_head for doubly-linked list of buffers still remaining to be
flushed before an old transaction can be checkpointed.
Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
---
fs/jbd/checkpoint.c | 119 +++
fs/jbd/commit.c |
Thanks David, but if you read my original post in full you'll see that I've
tried that, and while I can start the write out sooner by lowering
/proc/sys/vm/dirty_ratio , it makes no difference to the results that I am
getting. I still seem to run out of steam after only 50 seconds where it shou
Here it is.
>>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 10:50:01 >>>
On Thursday 08 September 2005 18:07, Jan Beulich wrote:
> (Note: Patch also attached because the inline version is certain to
get
> line wrapped.)
>
> Declare NMI_VECTOR and handle it in the IPI sending code.
I would apply it no
>>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 10:54:11 >>>
>On Thursday 08 September 2005 18:04, Jan Beulich wrote:
>> (Note: Patch also attached because the inline version is certain to
get
>> line wrapped.)
>>
>> Allow building the x86-64 kernels with frame pointers if so needed.
>
>This doesn't wo
>>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 10:57:07 >>>
>On Thursday 08 September 2005 18:03, Jan Beulich wrote:
>> (Note: Patch also attached because the inline version is certain to
get
>> line wrapped.)
>>
>> While only cosmetic for x86-64, this adjusts the cmpxchg code
>> appearantly
>> inheri
Akinobu Mita <[EMAIL PROTECTED]> wrote:
>
> The following 6 patches cleanup the jbd code and kill about 200 lines.
>
Thanks, but I'm not inclined to apply them.
a) Maybe 70-80% of the Linux world uses this filesystem. We need to be
very cautious in making changes to it.
b) A relatively larg
Hello
I have Nikon Coolpix 2000 digital camera which was working well on my
old Linux 2.6.? machine. After moving to a different one while the old
one is not accessible, where the new one has Linux version 2.6.13, I
found it doesn't work anymore. When compact flash is inside the camera,
camera tur
NTFS: Support more clean journal ($LogFile) states.
- Support journals ($LogFile) which have been modified by chkdsk. This
means users can boot into Windows after we marked the volume dirty.
The Windows boot will run chkdsk and then reboot. The user can then
immedia
[PATCH 4/25] NTFS: Fix two nasty runlist merging bugs that had gone unnoticed
so far. Thanks to Stefano Picerno for the bug report.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/runlist.c |5 +++--
2 files changed, 5 insertions(+), 2 deletio
Hi Linus, please pull from
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aia21/ntfs-2.6.git/HEAD
This is the next NTFS update containing a ton of bug fixes several of
which fix bugs people actually hit in the big bad world...
Please apply. Thanks!
I am sending the changesets as actual pat
NTFS: Allow highmem kmalloc() in ntfs_malloc_nofs() and add _nofail() version.
- Modify fs/ntfs/malloc.h::ntfs_malloc_nofs() to do the kmalloc() based
allocations with __GFP_HIGHMEM, analogous to how the vmalloc() based
allocations are done.
- Add fs/ntfs/malloc.h::ntfs_malloc_nofs_nofail() wh
[PATCH 5/25] NTFS: Remove two bogus BUG_ON()s from fs/ntfs/mft.c.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |1 +
fs/ntfs/mft.c |2 --
2 files changed, 1 insertions(+), 2 deletions(-)
8bb735216a0675e247bbe8b8b92c09d6884d1a17
diff --git a/fs/ntfs/Ch
[PATCH 3/25] NTFS: Use ntfs_malloc_nofs_nofail() in ntfs_runlists_merge()
in the two critical regions. This means we no longer need to
panic() when the allocation fails as it now cannot fail.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |3 ++
fs/
On Friday 09 September 2005 07:25, Chuck Ebbert wrote:
> This is the same patch that went into i386 just before 2.6.13
> came out. I still can't build 64-bit user apps, so I tested
> with program (see below) in 32-bit mode on 64-bit kernel:
Applied thanks.
-Andi
-
To unsubscribe from this list:
[PATCH 21/25] NTFS: Fix fs/ntfs/aops.c::ntfs_{read,write}_block() to handle the
case
where a concurrent truncate has truncated the runlist under our feet.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/aops.c| 51 +
[PATCH 7/25] NTFS: Report unrepresentable inodes during ntfs_readdir() as
KERN_WARNING
messages and include the inode number. Thanks to Yura Pakhuchiy for
pointing this out.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |3 +++
fs/ntfs/dir.c |
[PATCH 17/25] NTFS: Fixup handling of sparse, compressed, and encrypted
attributes in
fs/ntfs/inode.c::ntfs_read_locked_{,attr_,index_}inode().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2
fs/ntfs/inode.c | 215 --
On Friday 09 September 2005 11:16, Jan Beulich wrote:
> >>> Andi Kleen <[EMAIL PROTECTED]> 09.09.05 10:54:11 >>>
> >
> >On Thursday 08 September 2005 18:04, Jan Beulich wrote:
> >> (Note: Patch also attached because the inline version is certain to
>
> get
>
> >> line wrapped.)
> >>
> >> Allow buil
[PATCH 20/25] NTFS: Optimize fs/ntfs/aops.c::ntfs_write_block() by extending
the page
lock protection over the buffer submission for i/o which allows the
removal of the get_bh()/put_bh() pairs for each buffer.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/Change
[PATCH 19/25] NTFS: Fixup handling of sparse, compressed, and encrypted
attributes in
fs/ntfs/aops.c::ntfs_writepage().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 +
fs/ntfs/aops.c| 104 -
2
[PATCH 12/25] NTFS: Add fs/ntfs/attrib.[hc]::ntfs_resident_attr_value_resize().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |1 +
fs/ntfs/attrib.c | 40
fs/ntfs/attrib.h |2 ++
3 files changed, 43 insertions(+)
[PATCH 22/25] NTFS: Fixup handling of sparse, compressed, and encrypted
attributes in
fs/ntfs/aops.c::ntfs_readpage().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |5 ++---
fs/ntfs/aops.c| 41 -
2 files cha
[PATCH 16/25] NTFS: Truncate {a,c,m}time to the ntfs supported time granularity
when
updating the times in the inode in ntfs_setattr().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/inode.c | 12 +++-
2 files changed, 9 inserti
[PATCH 10/25] NTFS: Fix a bug in fs/ntfs/index.c::ntfs_index_lookup(). When
the returned
index entry is in the index root, we forgot to set the @ir pointer in
the index context. Thanks for Yura Pakhuchiy for finding this bug.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
--
[PATCH 23/25] NTFS: Fix page_has_buffers()/page_buffers() handling in
fs/ntfs/aops.c.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |1 +
fs/ntfs/aops.c| 38 +-
2 files changed, 22 insertions(+), 17 deletions(-)
a01ac
[PATCH 18/25] NTFS: Make ntfs_write_block() not instantiate sparse blocks if
they are zero.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/aops.c| 21 +
2 files changed, 23 insertions(+), 0 deletions(-)
8dcdebafb848415e
[PATCH 24/25] NTFS: Improve scalability by changing the driver global spin lock
in
fs/ntfs/aops.c::ntfs_end_buffer_async_read() to a bit spin lock
in the first buffer head of a page.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |3 +++
fs/ntfs/aop
[PATCH 25/25] NTFS: 2.1.24 release and some minor final fixes.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
Documentation/filesystems/ntfs.txt | 12
fs/ntfs/ChangeLog |4 +++-
fs/ntfs/Makefile |2 +-
fs/ntfs/aops.c
[PATCH 14/25] NTFS: Fix handling of sparse attributes in
ntfs_attr_make_non_resident().
Also, add BUG() checks to ntfs_attr_make_non_resident() and
ntfs_attr_set() to ensure that these functions are never called
for compressed or encrypted attributes.
Signed-off-by: Anton Altapa
[PATCH 13/25] NTFS: Fix several bugs in fs/ntfs/attrib.c.
- Fix a bug in ntfs_map_runlist_nolock() where we forgot to protect
access to the allocated size in the ntfs inode with the size lock.
- Fix ntfs_attr_vcn_to_lcn_nolock() and ntfs_attr_find_vcn_nolock() to
return LCN_ENOENT when there i
[PATCH 9/25] NTFS: Add ntfs_rl_punch_nolock() which punches a caller specified
hole into a runlist.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2
fs/ntfs/runlist.c | 284 +
fs/ntfs/runlist.h |3 +
3
[PATCH 15/25] NTFS: Fix cluster (de)allocators to work when the runlist is NULL
and more
importantly to take a locked runlist rather than them locking it
which leads to lock reversal.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |3 +++
fs/ntfs/l
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
> On 08/09/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> >
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/
>
> [EMAIL PROTECTED]:~$ cat /proc/meminfo
> MemTotal: 893824 kB
> [---cut---]
> VmallocCh
[PATCH 11/25] NTFS: Remove bogus setting of PageError in
ntfs_read_compressed_block().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |1 +
fs/ntfs/compress.c |8
fs/ntfs/file.c |9 +++--
3 files changed, 8 insertions(+), 10 deletions(
[PATCH 6/25] NTFS: Fix handling of valid but empty mapping pairs array in
fs/ntfs/runlist.c::ntfs_mapping_pairs_decompress().
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/runlist.c |3 +++
2 files changed, 5 insertions(+), 0 deletions(
[PATCH 8/25] NTFS: Change ntfs_rl_truncate_nolock() to throw away the runlist
if the new
length is zero.
Signed-off-by: Anton Altaparmakov <[EMAIL PROTECTED]>
---
fs/ntfs/ChangeLog |2 ++
fs/ntfs/runlist.c | 14 +-
2 files changed, 15 insertions(+), 1 deletions(-)
3ffc
>>> Tom Rini <[EMAIL PROTECTED]> 08.09.05 17:33:14 >>>
>On Thu, Sep 08, 2005 at 05:03:58PM +0200, Jan Beulich wrote:
>It's possible to do this a bit differently, if I'm guessing right at
>what NLKD does. The following is from the KGDB patches (trimmed of
some
>other, unrelated to the notify part c
> But why would anyone want frame pointers on x86-64?
I'd put the question differently: Why should x86-64 not allow what
other architectures do?
But of course, I'm not insisting on this patch to get in, it just
seemed an obvious inconsistency...
Jan
-
To unsubscribe from this list: send the line
Grant Coady <[EMAIL PROTECTED]> wrote:
>
> On Thu, 8 Sep 2005 05:30:42 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/
>
> Hi Andrew,
>
> After this error:
>
> CC drivers/parport/parport_pc.o
> driv
>>> Zwane Mwaikambo <[EMAIL PROTECTED]> 08.09.05 19:37:20 >>>
>On Thu, 8 Sep 2005, Jan Beulich wrote:
>
>> diff -Npru 2.6.13/arch/i386/kernel/traps.c
>> 2.6.13-i386-die-irq/arch/i386/kernel/traps.c
>> --- 2.6.13/arch/i386/kernel/traps.c 2005-08-29 01:41:01.0
>> +0200
>> +++ 2.6.13-i386-die
The soon to be released smartmontools 5.34 uses the
READ DEFECT DATA command on SCSI disks. A disk that
has defect list entries (or worse, an increasing number
of them) is at risk.
Currently the first invocation of smartctl causes this:
scsi: unknown opcode 0x37
message to appear the console an
On Thu, 8 Sep 2005, Andy Fleming wrote:
The new PHY Layer (drivers/net/phy/*) can provide all these features
for you without much difficulty, I suspect.
As pointed to be Andrew a few days ago, this driver supports a lot of
chips - for most of them the test hardware would be hard to come by
a
>I don't think it's a good idea to have two different ways
>to do kallsyms. Either we should always use your new
>way in standard KALLSYMS or not do it at all.
I agree, but I wanted to retain the old mechanism not the least because
of the space constraints you mention.
>The major decision factor
A couple of comments - see below.
On Fri, Sep 09, 2005 at 04:49:27AM +0200, Mathias Adam wrote:
> --- linux-2.6.13-org/drivers/serial/8250.c2005-08-29 01:41:01.0
> +0200
> +++ linux-2.6.13/drivers/serial/8250.c2005-09-09 02:16:49.0
> +0200
> @@ -1665,7 +1665,7 @@
>
On Fri, Sep 09 2005, Douglas Gilbert wrote:
> The soon to be released smartmontools 5.34 uses the
> READ DEFECT DATA command on SCSI disks. A disk that
> has defect list entries (or worse, an increasing number
> of them) is at risk.
>
> Currently the first invocation of smartctl causes this:
>
--- David Brownell <[EMAIL PROTECTED]> wrote:
> > Date: Wed, 7 Sep 2005 19:38:43 +0100 (BST)
> > From: Mark Underwood <[EMAIL PROTECTED]>
> > ...
> >
> > I see several posabiltiys of how SPI devices could
> be
> > connected to an adapter.
>
> Certainly, and all are addressed cleanly by the kind
On 9/9/05, Anton Altaparmakov <[EMAIL PROTECTED]> wrote:
> -static inline void *ntfs_malloc_nofs(unsigned long size)
> +static inline void *__ntfs_malloc(unsigned long size,
> + unsigned int __nocast gfp_mask)
> {
> if (likely(size <= PAGE_SIZE)) {
> BUG_ON(!s
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > arch/x86_64/pci/built-in.o(.init.text+0xa88): In function
> `pci_acpi_scan_root':
> > : undefined reference to `pxm_to_node'
> > make: *** [.tmp_vmlinux1] Error 1
> > 09/08/05-06:52:31 Build the kernel. Failed rc = 2
> > 09/08/05-06:52:31 build: ker
schönfeld / in-medias-res wrote:
Hi Petr,
the two servers is that the one with the problems does run a nagios nrpe
server and some plugins, e.g. to check disk space on the novell disk,
while the other server does not. Now i found that heavy operations on
the filesystem (e.g. stat'ing many small
On Fri, 9 Sep 2005, Jan Beulich wrote:
> > But why would anyone want frame pointers on x86-64?
>
> I'd put the question differently: Why should x86-64 not allow what
> other architectures do?
>
> But of course, I'm not insisting on this patch to get in, it just
> seemed an obvious inconsistency..
On Friday 09 September 2005 12:41, Andrew Morton wrote:
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > arch/x86_64/pci/built-in.o(.init.text+0xa88): In function
`pci_acpi_scan_root':
> > > : undefined reference to `pxm_to_node'
> > >
> > > make: *** [.tmp_vmlinux1] Error 1
> > > 09/08/05-06:52
The legacy PIC's name is "i8259".
Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]>
diff -upr linux-2.6.13-rc6/arch/i386/kernel/io_apic.c
linux-2.6.13/arch/i386/kernel/io_apic.c
--- linux-2.6.13-rc6/arch/i386/kernel/io_apic.c 2005-08-08 11:46:00.0
+0200
+++ linux-2.6.13/arch/i386/kernel
On Friday 09 September 2005 12:45, Hugh Dickins wrote:
> On Fri, 9 Sep 2005, Jan Beulich wrote:
> > > But why would anyone want frame pointers on x86-64?
> >
> > I'd put the question differently: Why should x86-64 not allow what
> > other architectures do?
> >
> > But of course, I'm not insisting o
On Fri, 2005-09-09 at 13:36 +0300, Pekka Enberg wrote:
> On 9/9/05, Anton Altaparmakov <[EMAIL PROTECTED]> wrote:
> > -static inline void *ntfs_malloc_nofs(unsigned long size)
> > +static inline void *__ntfs_malloc(unsigned long size,
> > + unsigned int __nocast gfp_mask)
> > {
> >
On Fri, 09 Sep 2005 at 11:23 +, Andi Kleen wrote:
> Indeed. Someone must have fixed it. But why would anyone want frame pointers
> on x86-64?
Oprofile can use it, I though it was already used but apparently only
to backtrace userspace actually.
--
Philippe Elie
-
To unsubscribe from thi
Petr Vandrovec schrieb:
> schönfeld / in-medias-res wrote:
>
>> Hi Petr,
>>
>> the two servers is that the one with the problems does run a nagios nrpe
>> server and some plugins, e.g. to check disk space on the novell disk,
>> while the other server does not. Now i found that heavy operations on
On Thu, Sep 08, 2005 at 11:47:42PM +0200, Sam Ravnborg wrote:
> mips has it own private gen-asm-offset macro,
>
> The important part being:
>
> sed -ne "/^@@@/s///p"; \
>
> compared to the generic one:
>
> sed -ne "/^->/{s:^->\([^ ]*\) [\$$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3
> */:; s:->::
On Fri, 9 Sep 2005, Anton Altaparmakov wrote:
> Also note I only use the ntfs_malloc_nofs() wrapper if I have to. If I
> know how much I am allocating or at least know that the maximum is quite
> small, I use kmalloc() directly. It is pretty much only for the runlist
> allocations that I use the
On Fri, Sep 09, 2005 at 12:59:04PM +0200, Karsten Wiese wrote:
> The legacy PIC's name is "i8259".
>
> Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]>
Indeed, i82559 is an Ethernet NIC.
Signed-off-by: Vojtech Pavlik <[EMAIL PROTECTED]>
> diff -upr linux-2.6.13-rc6/arch/i386/kernel/io_apic.c
>
On Fri, 9 Sep 2005, Andi Kleen wrote:
>
> It won't give more accurate backtraces, not even on i386 because show_stack
> doesn't have any code to follow frame pointers.
Ah, right. I'm using kdb with it. (And my recollection of when
show_stack did have a framepointer version, is that it was hopel
On Fri, Sep 09, 2005 at 01:07:02PM +0200, Philippe Elie wrote:
> On Fri, 09 Sep 2005 at 11:23 +, Andi Kleen wrote:
>
>
> > Indeed. Someone must have fixed it. But why would anyone want frame
> > pointers
> > on x86-64?
>
> Oprofile can use it, I though it was already used but apparently o
1 - 100 of 369 matches
Mail list logo
