I can't readily think of a scenario where a load/store or RMW gets
cancelled, except perhaps for a prefetch or data abort. But in that case an
exception should be thrown even when your code starts the read/load I'd have
thought.
Is this based on a specific problem you're experiencing ?
For example
On Mon, Mar 9, 2009 at 11:29 PM, Vishal Thanki wrote:
> its declared in linux/time/timekeeping.c
> ref : http://lxr.linux.no/linux+v2.6.28.7/kernel/time/timekeeping.c#L45
It is defined there, not declared. The declaration is here-
http://lxr.linux.no/linux+v2.6.28.7/include/linux/time.h#L100
BTW
Hi all,
After reading the The Linux Kernel Module Programming Guide, I have
written a very simple module that reads the value of variable xtime
declared in time.h and displays the output in /proc/xtime_procfs -
http://docs.google.com/Doc?id=dftrdgx_0hsjqkhfs
Here is the Makefile-
http://docs.goog
Hi
Can u say a scenario where load/store micro ops gets cancelled ?
Does this happen becos of speculative execution ?
--
With Love..
. .Shino
On Mon, Mar 9, 2009 at 11:50 PM, Peter Teoh wrote:
> as far as I can remember, in x86 architecture, hardware-wise, it is
> NOT possible to enable NX. U may do anything via software, but it
> will not be enabled. NX feature is only for 64bit OS.
>
No, NX is available for 32bit Linux, as long a
Chauhan wrote:
> While going through vmscan.c, I found references to mem_cgroup. What
> kind of group is it? When is it used?
>
Documentation/cgroups/cgroups.txt
Documentation/cgroups/memory.txt
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linu
Hi Stoyan/Nelson,
>> BUG_ON(expect != sizeof(foo));
> IIRC sizeof is not actually a function. Its value is known by the
compiler.
Correct - sizeof is simply a compile time operator.
Its value is constant (iow hardcoded) at runtime.
>> also what about bit operations? so like BUG_ON(s & 3); would
Hi,
I've posted a reply to the atomic_t topic, but I think HTML (which I
normally never use for Email) is blocked - dunno.
As before, ran 2.6.26.3 kernel through Doxygen and this is what it tells me
:
(I'm ccing this to you as well - if I notice that this post still indeed is
blocked, I'll re
Hi,
thank you for the reply.
I'll give it a try tomorrow. But I assume this is not a kernel -
configuration problem. Because the development board that came with the
dnp9200 was running well with the same kernel 2.6.10 + same configuration.
So it must be a hardware problem that linux can't handl
On Tue, Mar 10, 2009 at 3:59 AM, Stoyan Gaydarov wrote:
> I know that function calls should not normally be inside the BUG_ON
> params but what about sizeof?
>
> so would something like this work as intended:
>
> BUG_ON(expect != sizeof(foo));
IIRC sizeof is not actually a function. Its value is
hi
did you check your initial console?
what do you get on kernel 2.4 when you say:
cat /proc/cmdline
May be the name for your initial console changed
from ttyS0 (2.4) to ttySMX0 (2.6) or some thing similar.
Probably you will find the name for it in
drivers/serial/the_driver_which_is_used_for
I know that function calls should not normally be inside the BUG_ON
params but what about sizeof?
so would something like this work as intended:
BUG_ON(expect != sizeof(foo));
also what about bit operations? so like BUG_ON(s & 3); would that
still be ok since it doesn't actually modify the origi
Hello there,
we are developing an board for the dnp9200 SOC
(http://www.dilnetpc.com/dnp0069.htm).
We got kernel 2.4.27 running with the board, boots fine, serial port is
working, ethernet is working, everything is good.
but when i try to boot kernel 2.6.10, it hangs.
What could be the cause?
While going through vmscan.c, I found references to mem_cgroup. What
kind of group is it? When is it used?
Thanks
Regards
Chauhan
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ
Hi
On Mon, Mar 9, 2009 at 9:08 AM, Mike Christie wrote:
> Hi,
>
> I thought in older linux driver books and docs on the internet it said that
> you should not rely on a atomic_t being a certain size, because in some
> archs it may be different.
>
> However, in reading Documentation/atomic_ops.txt
On Mon, Mar 09, 2009 at 05:06:17PM +0530, nidhi mittal wrote:
> hey i saw this ...directory ...found its a gud idea ...
> may be difficult as we will have to first understand whole working before
> adding or doing work on single line ...
Like you would any other project, correct?
> can we have so
as far as I can remember, in x86 architecture, hardware-wise, it is
NOT possible to enable NX. U may do anything via software, but it
will not be enabled. NX feature is only for 64bit OS.
http://en.wikipedia.org/wiki/NX_bit
http://en.wikipedia.org/wiki/X86-64
On Mon, Mar 9, 2009 at 4:27 AM, N
you can use readelf to dump out the elf information of your .ko
Where do static variables get stored? Definitely not in the stack. Hence your
observation.
- durga
From: yogeshwar sonawane
To: kernelnewbies
Sent: Monday, March 9, 2009 3:36:19 PM
Subject: Re:
hey i saw this ...directory ...found its a gud idea ...
may be difficult as we will have to first understand whole working before
adding or doing work on single line ...
can we have some doc related to it
or anything as i wd want to work on it ..
Nidhi
On Fri, Mar 6, 2009 at 11:12 PM, Greg K
Hi Yogeshwar,
The reason the panic disappeared is because a "static" object cannot live on
the stack. It will be stored in the global data area.
A static local is really like a global, the difference is scope.
> Can one dump more information using some command on a .ko object ?
I think the binar
Hi,
Continuing my discussion, i tried one more thing.
I changed my array declaration from unsigned int array[] to static
unsigned int array[].
Then the kernel panic has disappeared. Now things are working fine.
For ELF file format, one is aware of the different section like code,bss etc
Simi
Hi,
I inspect my Linux memory, and it seems that there is no area that
prohibite execution like I expected (using NX bit in modern CPU). That
really surprises me.
I looked at some potential data areas exported in System.map file, like:
- mark_rodata_ro
- sysctl_data
- new_cpu_data
- boot_cpu_dat
On Sun, Mar 8, 2009 at 7:29 AM, Rik van Riel wrote:
> NAHieu wrote:
>>
>> hi,
>>
>> i heard that it is possible to have HIGHMEM4G and PAE options
>> combined. Is that really possible?
>
> That is called HIGHMEM64G.
>
I asked because on 2.6.18, HIGHMEM4G automatically enables PAE option
(CONFIG_X8
23 matches
Mail list logo