Re: NMI broadcast causes divide error?

On Thu, May 29, 2008 at 10:25 AM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > On 5/29/08, Peter Teoh <[EMAIL PROTECTED]> wrote: >> Hi Vegard, I have some questions for you. >> > > [...] > >> Second, your present tried to retain the CR3 value, but change

Re: NMI broadcast causes divide error?

On 5/29/08, Peter Teoh <[EMAIL PROTECTED]> wrote: > Hi Vegard, I have some questions for you. > [...] > Second, your present tried to retain the CR3 value, but change the > contents of the page table insteadbut has problem with > multiprocessor. > > How about the other way round - change

Re: NMI broadcast causes divide error?

On Fri, May 23, 2008 at 4:55 PM, Peter Teoh <[EMAIL PROTECTED]> wrote: > It is not spamming, it is educationthank for the info. BTW...I > think u gave me an idea now.. > > Currently your kmemcheck is restricted to only one CPU. Why not > ALWAYS enable all the CPU to run at the same tim

Re: NMI broadcast causes divide error?

On Fri, May 23, 2008 at 12:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to broadcast an NMI like this: > >send_IPI_allbutself(NMI_VECTOR); > > But when I do this, I get a divide error: > > ... > CPU: L1 I cache: 8K > CPU:

Re: NMI broadcast causes divide error?

On Fri, May 23, 2008 at 1:26 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > On Fri, May 23, 2008 at 12:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I am trying to broadcast an NMI like this: >> >>send_IPI_allbutself(NMI_VECT

NMI broadcast causes divide error?

Hi, I am trying to broadcast an NMI like this: send_IPI_allbutself(NMI_VECTOR); But when I do this, I get a divide error: ... CPU: L1 I cache: 8K CPU: L2 cache: 128K CPU1: Intel Pentium II (Klamath) stepping 03 checking TSC synchronization [CPU#0 -> CPU#1]: passed. Brought up 2 CPUs Tot

Re: Deferring work in the page fault handler

On Thu, May 22, 2008 at 7:25 PM, Peter Teoh <[EMAIL PROTECTED]> wrote: > Thanks for the reply. I would appreciate if someone can help to > clear just a few more doubts > Hi, no problem :-) > On Thu, May 22, 2008 at 7:31 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: &

Re: Deferring work in the page fault handler

On 5/22/08, Peter Teoh <[EMAIL PROTECTED]> wrote: > On Wed, May 21, 2008 at 6:04 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > > In the kmemcheck code I take a lot of page faults from any kernel > > context (with interrupts enabled or disabled). This means that there

Re: Deferring work in the page fault handler

On 5/22/08, Mulyadi Santosa <[EMAIL PROTECTED]> wrote: > Hi man > > First, kudos for your work on kmemchecki haven't tried it by > myself but I think it's a cool piece of codes. > > > On Wed, May 21, 2008 at 5:04 PM, Vegard Nossum <[EMAIL PR

Re: Deferring work in the page fault handler

On Wed, May 21, 2008 at 2:13 PM, Rene Herman <[EMAIL PROTECTED]> wrote: > On 21-05-08 14:08, Rene Herman wrote: > >> On 21-05-08 12:04, Vegard Nossum wrote: >> >>> In addition to this, I must _not_ access any memory allocated by >>> kmalloc(), as this

Deferring work in the page fault handler

Hi, In the kmemcheck code I take a lot of page faults from any kernel context (with interrupts enabled or disabled). This means that there are a lot of things I can't do. Taking locks is dangerous while handling a page fault occurring in interrupt context. In addition to this, I must _not_ access

Re: ask for help. question about snprintf()

On Tue, May 20, 2008 at 11:36 AM, Rene Herman <[EMAIL PROTECTED]> wrote: > On 20-05-08 05:47, Payphone LIOU wrote: > >> in a kernel modules, i used "snprintf()" to ouput some strings to the >> terminal. > > snprintf() doesn't output to anything; it writes to the buffer it's given as > its first par

[RFC][PATCH] proc: add "stacktrace" file

it up. Vegard >From 29a2cff09e52ea9a7ecc4bef3e52012d1dd3d525 Mon Sep 17 00:00:00 2001 From: Vegard Nossum <[EMAIL PROTECTED]> Date: Fri, 16 May 2008 16:33:29 +0200 Subject: [PATCH] proc: add "stacktrace" file This patch adds a /proc//stacktrace file which will show the current k

Re: Newbies question regarding git

Hi, On Sat, Apr 5, 2008 at 12:40 PM, Manish Katiyar <[EMAIL PROTECTED]> wrote: > I am trying to configure my development environment and thus trying my > hands with git to keep myself updated with kernel and e2fsprogs. I > could setup git to pull the latest images, however I have few basic > q

Re: atomic operation in 32 bit but no in 64!?

On Fri, Feb 29, 2008 at 3:33 PM, Peter Teoh <[EMAIL PROTECTED]> wrote: > On Fri, Feb 29, 2008 at 10:18 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > > On Fri, Feb 29, 2008 at 1:34 AM, Peter Teoh <[EMAIL PROTECTED]> wrote: > > > Sorry this part really puzzled

Re: atomic operation in 32 bit but no in 64!?

On Fri, Feb 29, 2008 at 1:34 AM, Peter Teoh <[EMAIL PROTECTED]> wrote: > Sorry this part really puzzled me > > On Sat, Feb 9, 2008 at 8:10 AM, Rene Herman <[EMAIL PROTECTED]> wrote: > > In the CPU's ALU. inode->i_size is a 64_bit integer, and access to it is > > atomic on 64-bit. On a 32-b

Re: Minimum pentium class machine to do kernel testing?

least a little bit. But knowing your requirements and/or intentions would probably help us answer your question. Good luck. Kind regards, Vegard Nossum -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ

Re: x86 pages, page tables, and page table entries

On Jan 22, 2008 10:31 AM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > On Jan 21, 2008 11:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am experiencing something strange about pages and ptes on x86. I am > > calling alloc_pages() with orde

Re: x86 pages, page tables, and page table entries

On Jan 21, 2008 11:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > Hi, > > I am experiencing something strange about pages and ptes on x86. I am > calling alloc_pages() with order = 1 (should be 2 pages). This returns > a struct page with virtual address c780 (retur

x86 pages, page tables, and page table entries

allocator. Does anybody know immediately what I am doing wrong here? Help is appreciated. Thanks. Kind regards, Vegard Nossum -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ

Re: Deficient volume knob

On Jan 8, 2008 10:59 AM, Daniel Cheng <[EMAIL PROTECTED]> wrote: > Vegard Nossum wrote: > > So it seems that the wheel is not hard-wired to the sound card or > > speakers at all. How would I go about to making it change the sound > > volume? I don't even know wh

Deficient volume knob

driver? Register an event listener somewhere in ALSA? Or is this a job for user-space alone? I would be grateful for a helping hand! Thanks. Kind regards, Vegard Nossum -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ

Re: who defines __KERNEL__ ?

On Dec 12, 2007 9:26 AM, Ramagudi Naziir <[EMAIL PROTECTED]> wrote: > Hi all, > > Should I define __KERNEL__ in my in-tree kernel module (that may > be compiled as built-in if the user wanted) ? No. > Or does it gets defined automatically by kbuild ? $ grep __KERNEL__ Makefile KBUILD_CPPFLAGS :=

Re: sys_open fails with error 14

ith __user, meaning it expects an address that comes from userspace, not the kernel space. And why will this function fail if you provide it with a kernel address? It's rather simple; the kernel must not allow userspace to pass kernel addresses in its system calls, otherwise the user proc

Re: Generate assembly listings of the kernel

ng will be output. You may also use objdump -d to give the disassembly of an object file. This can sometimes be useful if you want to see addresses or avoid some of the "noise" that gcc adds. Good luck. Kind regards, Vegard Nossum -- To unsubscribe from this list: send an email with &

Re: Linking/comping with clock.c

Hello, On Dec 4, 2007 4:18 PM, Peter Poulsen <[EMAIL PROTECTED]> wrote: > I now have this peice of code that uses the clock. However, the > 'struct clk' is > defined in clock.c, so not suprisingly it refuses to compile. I have > no idea how > other manage to make their code compile when they use

Re: another questions about early initrd issues

Hi, On Dec 4, 2007 2:59 PM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > all right, let me make sure i understand what's happening here. if > you look at the tail end of init/initramfs.c, you can see in the > routine populate_rootfs() where that "checking if image is > initramfs..." message is b

Re: OT: Kernel Copyright line

On Nov 20, 2007 11:20 PM, Ramagudi Naziir <[EMAIL PROTECTED]> wrote: > Hello... > > I got a slightly off topic question i've been pondering about lately.. > > When someone writes in the header of his kernel file: > > Copyright (C) 2007 My Name > > What does the 2007 mean ? I sometimes see lines lik

Re: Need help with debugging (gcc bug?)

On Nov 20, 2007 12:16 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > Hello, > > Running kmemcheck, I got the following: > kmemcheck: Caught uninitialized read from EIP = c11aeba6 > (sock_init_data+0xa6/0x17a), address c341a024, size 32 > [] error_code+0x72/0x78 > [

Re: Need help with debugging (gcc bug?)

On Nov 20, 2007 12:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > On Nov 20, 2007 12:16 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > > Here, offsetof(struct socket, type) = 0x24, like the one used in the > > reads/writes. The type here is short, on 386 that's

Need help with debugging (gcc bug?)

x24, like the one used in the reads/writes. The type here is short, on 386 that's 16 bits. So why is gcc later reading 32 bits off the same address, is that really legal? Shouldn't that really have been a MOVZWL? Or did I miss something obvious? Kind regards, Vegard Nossum -- To unsubscr

Re: Page faults in interrupt context

On Nov 17, 2007 9:02 AM, Rene Herman <[EMAIL PROTECTED]> wrote: > On 17-11-07 05:56, Peter Teoh wrote: > You get a scary "scheduling while atomic" message in the kernel log. In > atomic context, which is the context you're in inside an interrupt handler, > you must never do things which can cause y

Page faults in interrupt context

Hi, I have these questions regarding page faults and interrupts on the 386. Can page faults happen while a CPU is executing an interrupt handler? As far as I know, interrupt handlers are entered with interrupts disabled. Does this mask page faults? If so, what happens when the kernel faults on sw

Re: diff between strnicmp() and strncasecmp()?

On 10/2/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > maybe i'm just missing something obvious, but is there any > difference between the above routines defined in lib/string.c? they > both appear to be length-limited, case-insensitive string > comparisons. I think they're the same, too, bu

Re: git branch rename ?

On 9/23/07, Ramagudi Naziir <[EMAIL PROTECTED]> wrote: > hello people, > > do you know if there's a simple way to rename a branch in git ? > or is the only way to do so would be to create a new branch and pull/push > the old branch into it ? If you run git-branch --help, this will tell you command

Re: "retain_initrd" versus "keepinitrd"?

On 9/19/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > if they represent the same thing, it would seem to make sense to > just drop support for "keepinitrd", no? If they are truly the same, then maybe something like printk WARN "keepinitrd is deprecated. Please use retain_initrd instead."? V

Re: Difference between ppc and powerpc architectures

ght on this issue please? This has been asked on this list before :) See http://www.spinics.net/lists/newbies/msg27500.html and the replies. In short, ppc/ is in the process of being converted to powerpc/. Kind regards, Vegard Nossum -- To unsubscribe from this list: send an email with "