On Fri, Apr 16, 2021 at 8:18 AM Corentin Labbe
wrote:
>
> Hello
>
> I am converting Documentation/devicetree/bindings/usb/faraday,fotg210.txt to
> yaml with the patch attached below.
> But validating it give me:
> Documentation/devicetree/bindings/usb/faraday,fotg210.example.dt.yaml:
> usb@68000
Message-
From: Paul E. McKenney
Sent: 01 May 2020 00:47
To: Atul Kulkarni
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need help on "Self Detected Stall on CPU"
On Thu, Apr 30, 2020 at 06:47:20PM +, Atul Kulkarni wrote:
> Dear Sir,
>
> Hope you are doing well. I have w
On Thu, Apr 30, 2020 at 06:47:20PM +, Atul Kulkarni wrote:
> Dear Sir,
>
> Hope you are doing well. I have watched your various conference videos and
> have read technical papers.
> We are facing an issue with CPU stall on our systems and I felt like there is
> no one better who can guide u
On Fri, Jan 18, 2019 at 5:23 PM Sai Prakash Ranjan
wrote:
>
> On 1/18/2019 4:50 PM, Pintu Agarwal wrote:
> Could you please tell which QCOM SoC this board is based on?
>
> >>>
> >>> Snapdragon 845 with kernel 4.9.x
> >>> I want to know from which subsystem it is triggered:drivers/soc/qco
On 1/18/2019 4:50 PM, Pintu Agarwal wrote:
Could you please tell which QCOM SoC this board is based on?
Snapdragon 845 with kernel 4.9.x
I want to know from which subsystem it is triggered:drivers/soc/qcom/
Irqchip driver is "drivers/irqchip/irq-gic-v3.c". The kernel you are
using is msm-4.
> >> Could you please tell which QCOM SoC this board is based on?
> >>
> >
> > Snapdragon 845 with kernel 4.9.x
> > I want to know from which subsystem it is triggered:drivers/soc/qcom/
> >
>
> Irqchip driver is "drivers/irqchip/irq-gic-v3.c". The kernel you are
> using is msm-4.9 I suppose or some
On 1/18/2019 4:18 PM, Pintu Agarwal wrote:
On Fri, Jan 18, 2019 at 3:54 PM Sai Prakash Ranjan
wrote:
Hi Pintu-san,
On 1/18/2019 3:38 PM, Pintu Agarwal wrote:
Hi All,
Currently, I am trying to debug a boot up crash on some qualcomm
snapdragon arm64 board with kernel 4.9.
I could find the cau
On Fri, Jan 18, 2019 at 3:54 PM Sai Prakash Ranjan
wrote:
>
> Hi Pintu-san,
>
> On 1/18/2019 3:38 PM, Pintu Agarwal wrote:
> > Hi All,
> >
> > Currently, I am trying to debug a boot up crash on some qualcomm
> > snapdragon arm64 board with kernel 4.9.
> > I could find the cause of the failure, but
Hi Pintu-san,
On 1/18/2019 3:38 PM, Pintu Agarwal wrote:
Hi All,
Currently, I am trying to debug a boot up crash on some qualcomm
snapdragon arm64 board with kernel 4.9.
I could find the cause of the failure, but I am unable to locate from
which subsystem/drivers this is getting triggered.
If y
Hi,
On Sat, 13 December 2014 Manish Yadav wrote:
> on my system (based on 2.6.16.17), i am trying to clear the cached
> memory but it is not being cleared.
>
> mars# free -m
> total used free sharedbuffers cached
> Mem: 925459465
On Mon, 3 Feb 2014, David Rientjes wrote:
On Mon, 3 Feb 2014, Vlastimil Babka wrote:
It seems to come from balloon_page_movable() and its test page_count(page) ==
1.
Hmm, I think it might be because compound_head() == NULL here. Holger,
this looks like a race condition when allocating a co
On Mon, 3 Feb 2014, Vlastimil Babka wrote:
> It seems to come from balloon_page_movable() and its test page_count(page) ==
> 1.
>
Hmm, I think it might be because compound_head() == NULL here. Holger,
this looks like a race condition when allocating a compound page, did you
only see it once o
On Mon, 3 Feb 2014, Michal Hocko wrote:
On Mon 03-02-14 14:29:22, Holger Kiehl wrote:
I have attached it. Please, tell me if you do not get the attachment.
I hoped it would help me to get a closer compiled code to yours but I am
probably using too different gcc.
I have an old gcc, it is 4.4
On 02/03/2014 05:20 PM, Michal Hocko wrote:
On Mon 03-02-14 14:29:22, Holger Kiehl wrote:
I have attached it. Please, tell me if you do not get the attachment.
I hoped it would help me to get a closer compiled code to yours but I am
probably using too different gcc.
Anyway I've tried to check
On Mon 03-02-14 14:29:22, Holger Kiehl wrote:
> I have attached it. Please, tell me if you do not get the attachment.
I hoped it would help me to get a closer compiled code to yours but I am
probably using too different gcc.
Anyway I've tried to check whether I can hook on something and it seems
t
[CCing linux-mm]
Does this ring bells? I haven't checked very deeply but it doesn't seem
to be fixed since 3.12.
Hoolger, could you post your config, please?
On Fri 31-01-14 21:12:27, Holger Kiehl wrote:
> Hello,
>
> today one of our system got a kernel bug message. It kept on running
> but mor
On Thu, Dec 5, 2013 at 11:36 AM, Jagan Teki wrote:
> On Thu, Dec 5, 2013 at 11:45 PM, Bjorn Helgaas wrote:
>> On Wed, Dec 4, 2013 at 11:30 PM, Jagan Teki wrote:
>>> On Wed, Dec 4, 2013 at 11:35 PM, Bjorn Helgaas wrote:
On Wed, Dec 4, 2013 at 10:00 AM, Jagan Teki
wrote:
> On Wed,
On Thu, Dec 5, 2013 at 11:45 PM, Bjorn Helgaas wrote:
> On Wed, Dec 4, 2013 at 11:30 PM, Jagan Teki wrote:
>> On Wed, Dec 4, 2013 at 11:35 PM, Bjorn Helgaas wrote:
>>> On Wed, Dec 4, 2013 at 10:00 AM, Jagan Teki
>>> wrote:
On Wed, Dec 4, 2013 at 8:41 PM, Bjorn Helgaas wrote:
> On Tue
On Wed, Dec 4, 2013 at 11:30 PM, Jagan Teki wrote:
> On Wed, Dec 4, 2013 at 11:35 PM, Bjorn Helgaas wrote:
>> On Wed, Dec 4, 2013 at 10:00 AM, Jagan Teki wrote:
>>> On Wed, Dec 4, 2013 at 8:41 PM, Bjorn Helgaas wrote:
On Tue, Dec 3, 2013 at 11:20 PM, Jagan Teki
wrote:
> Thanks f
On Wed, Dec 4, 2013 at 11:35 PM, Bjorn Helgaas wrote:
> On Wed, Dec 4, 2013 at 10:00 AM, Jagan Teki wrote:
>> On Wed, Dec 4, 2013 at 8:41 PM, Bjorn Helgaas wrote:
>>> On Tue, Dec 3, 2013 at 11:20 PM, Jagan Teki
>>> wrote:
Thanks for your quick response.
Please find my comments below.
On Wed, Dec 4, 2013 at 10:00 AM, Jagan Teki wrote:
> On Wed, Dec 4, 2013 at 8:41 PM, Bjorn Helgaas wrote:
>> On Tue, Dec 3, 2013 at 11:20 PM, Jagan Teki wrote:
>>> Thanks for your quick response.
>>> Please find my comments below.
>>>
>>> On Tue, Dec 3, 2013 at 11:09 PM, Bjorn Helgaas wrote:
>>
On Wed, Dec 4, 2013 at 8:41 PM, Bjorn Helgaas wrote:
> On Tue, Dec 3, 2013 at 11:20 PM, Jagan Teki wrote:
>> Thanks for your quick response.
>> Please find my comments below.
>>
>> On Tue, Dec 3, 2013 at 11:09 PM, Bjorn Helgaas wrote:
>>> On Tue, Dec 3, 2013 at 4:24 AM, Jagan Teki wrote:
H
On Tue, Dec 3, 2013 at 11:20 PM, Jagan Teki wrote:
> Thanks for your quick response.
> Please find my comments below.
>
> On Tue, Dec 3, 2013 at 11:09 PM, Bjorn Helgaas wrote:
>> On Tue, Dec 3, 2013 at 4:24 AM, Jagan Teki wrote:
>>> Hi,
>>>
>>> I have few question on Linux PCIe subsystem, I am t
Thanks for your quick response.
Please find my comments below.
On Tue, Dec 3, 2013 at 11:09 PM, Bjorn Helgaas wrote:
> On Tue, Dec 3, 2013 at 4:24 AM, Jagan Teki wrote:
>> Hi,
>>
>> I have few question on Linux PCIe subsystem, I am trying to understand
>> the PCIe on ARM platform.
>> 1. Compared
On Tue, Dec 3, 2013 at 4:24 AM, Jagan Teki wrote:
> Hi,
>
> I have few question on Linux PCIe subsystem, I am trying to understand
> the PCIe on ARM platform.
> 1. Compared to PCI, PCIe have an extra port functionalists/services
> which is implemented drivers/pci/pcie/* is it true?
Yes.
> 2. PCI
Ed,
On Thu, 6 Dec 2012, Edward Donovan wrote:
> So, let me try to confirm some things now, so I can learn as I go. To
> spell out what's in the new patch:
>
> The later line,
>
> action = desc->action;
>
> should have been this all along?
>
> action = action->next;
Yes. My bad :(
> And
> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: 2012年11月23日 PM 5:09
> To: Wang, Warner
> Cc: Wang, Song-Bo (Stoney)
> Subject: Re: need help on a DEADLOCK problem related to function try_one_irq()
>
> On Thu, 22 Nov 2012, Thomas Gleixn
de]
> Sent: 2012年11月23日 PM 5:09
> To: Wang, Warner
> Cc: Wang, Song-Bo (Stoney)
> Subject: Re: need help on a DEADLOCK problem related to function try_one_irq()
>
> On Thu, 22 Nov 2012, Thomas Gleixner wrote:
>
>> Warner,
>>
>> On Thu, 22 Nov 2012, Wang,
fy it on your environment?
Thanks,
-Warner
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: 2012年11月23日 PM 5:09
To: Wang, Warner
Cc: Wang, Song-Bo (Stoney)
Subject: Re: need help on a DEADLOCK problem related to function try_one_irq()
On Thu, 22 Nov 2012, Thomas
- Original Message -
From: "Cong Wang"
To: "Sachin Agarwalla"
Cc: "linux-kernel"
Sent: Tuesday, September 4, 2012 12:29:21 PM
Subject: Re: need help on development of linux kernel
On 08/30/2012 12:15 PM, Sachin Agarwalla wrote:
> Dear Sir/Madam,
>I have so
On 08/30/2012 12:15 PM, Sachin Agarwalla wrote:
Dear Sir/Madam,
I have some questions on development of linux kernel as follows:-
1.I want to know the location of files in linux kernel source code that
contains timer initialization and scheduler part.
Scheduler source code is in kernel/sche
> kernel-2.6.32-220.17.1.el6.x86_64
> kernel-2.6.32-220.23.1.el6.x86_64
> kernel-2.6.32-279.1.1.el6.x86_64
You need to contact your vendor for RHEL based kernels - they are
sufficiently different to upstream and from a long time back (with
backports).
This is the wrong place unless you can duplic
On Mon, 19 Nov 2007 00:29:46 -0500
Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Quoting Arjan van de Ven <[EMAIL PROTECTED]>:
>
> > if it's just for a custom case (as it sounds like).. a simple small
> > change to the pagefault handler sounds like the easiest thing to
> > do... (eg just a direct fun
Quoting Arjan van de Ven <[EMAIL PROTECTED]>:
if it's just for a custom case (as it sounds like).. a simple small
change to the pagefault handler sounds like the easiest thing to do...
(eg just a direct function call to what would have been your notifier)
Thanks! Actually, the idea is to make
On Sun, 18 Nov 2007 12:40:16 -0500
Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I'm trying to update a special tracing version of madwifi (driver for
> Atheros wireless cards) for Linux 2.6.24. This version was created to
> help reverse engineering the non-free part of the driver (also k
Kay Sievers wrote:
On 8/17/07, Larry Finger <[EMAIL PROTECTED]> wrote:
A new driver for the Broadcom BCM43xx devices has been written that uses
mac80211, rather than
softmac. The newest versions of the Broadcom firmware does not support all the
BCM devices.
Accordingly, a separate driver is be
On 8/17/07, Larry Finger <[EMAIL PROTECTED]> wrote:
> A new driver for the Broadcom BCM43xx devices has been written that uses
> mac80211, rather than
> softmac. The newest versions of the Broadcom firmware does not support all
> the BCM devices.
> Accordingly, a separate driver is being prepared
On Tuesday 24 July 2007, Devesh Sharma wrote:
> Hello all,
> I am facing some difficulty to implement compat_ioctl entry point in
> my driver code, please help me out to sort out the things.
> The ioctl is READ WRITE type,
> It takes one header structure as argument the structure is as follows,
> t
LOL ER wrote:
> Hello,
> I've been trying to make sense of how the kernel (on an i386) calls
> __do_IRQ() from do_IRQ() for the past few days to no avail. [...]
Since i386 was switched to the generic-IRQ architecture (see "Linux
generic IRQ handling" in Documentation/Docbook) it does not use __d
Daniel Walker wrote:
I'm not sure I'd get into "bisecting" one big patch. Especially if you
new to the patches inner workings..
You can bisect by kernel version using the older patches but it's
clearly limited,
http://people.redhat.com/mingo/realtime-preempt/older/
Actually working on this
On Mon, 2007-05-07 at 14:02 -0700, Tim Bird wrote:
> Daniel Walker wrote:
> > Are you sure you don't have HardIRQS in Threads enabled? Also are you
> > sure the kernel boots without the rt patch applied.
>
> Yes on both counts. I double-checked the configs. I'm using quilt
> and the RT patch is
Daniel Walker wrote:
> Are you sure you don't have HardIRQS in Threads enabled? Also are you
> sure the kernel boots without the rt patch applied.
Yes on both counts. I double-checked the configs. I'm using quilt
and the RT patch is at the end of my series, so it was easy to
pop the patch and tr
On Mon, 2007-05-07 at 11:47 -0700, Tim Bird wrote:
> I've applied patch-2.6.21-rt1 to a 2.6.21 kernel I'm using.
> With the patch applied, but no RT-Preempt options enabled,
> I'm getting network failures (eth0 transmit timeouts) on
> an OMAP board.
Are you sure you don't have HardIRQS in Threads
vjn wrote:
in my project i want to code the kernel such that when i plugged my usb it
should ask for password and check it in the kernel space . can anyone help
me
I think the correct solution is to use an excrypted mount, and issue the
mount command manually with the question in user space. T
vjn <[EMAIL PROTECTED]> wrote:
> in my project i want to code the kernel such that when i plugged my usb it
> should ask for password and check it in the kernel space . can anyone help
> me
No, since the kernel has no way to ask for input. Imagine a two-seated
machine with two keyboards, mice and
Hi,
Many thanks to Lennert Buytenhek.
Try applying:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4122/1
On 3/13/07, Ben Dooks <[EMAIL PROTECTED]> wrote:
On Tue, Mar 13, 2007 at 10:54:08AM +0530, Maxin John wrote:
> Hi,
>
> I have one question mach-ep93xx.
>
> In EP
On Tue, Mar 13, 2007 at 10:54:08AM +0530, Maxin John wrote:
> Hi,
>
> I have one question mach-ep93xx.
>
> In EP93xx IRQ handling part in core.c, the 2.6.19.2 kernel and
> newer kernels are configuring the 16 interrupts of the ports A & B
> together. The code is not using the interrupt capab
On Tue, 27 Feb 2007 13:22:56 + (GMT) Seetharam Dharmosoth wrote:
> Hi,
>
> I have one question regarding Crash Dump.
>
> Is Kernel-2.6.20 having the default Crash dump in main
> tree?
2.6.20 has a CRASH_DUMP config option for some processor
architectures, such as ia64, i386, x86_64, powerpc
Siddha, Suresh B wrote:
Sorry for my delayed response. I was away on vacation.
What platform is this? what do you mean by crashing? Do you see a
system freeze or oops?
Its xeon-64 bit processor,running in 32-bit compatibility
mode(i386-code). We have not seen this problem in x86_64 envioronm
Sorry for my delayed response. I was away on vacation.
What platform is this? what do you mean by crashing? Do you see a
system freeze or oops?
thanks,
suresh
On Mon, Jan 22, 2007 at 01:42:48PM +0530, Srinivasa Ds wrote:
> I saw cpuhotplug operations on 32-bit mode of xeon-64bit processors
> cr
> zach-dev2:~ $ ldd /bin/ls
> linux-gate.so.1 => (0xe000)
>
> This is the vsyscall entry point, which gets linked by ld into all processes.
Just a clarification... not GNU ld (the binutils thing), but /lib/ld-linux.so
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thu, 11 Aug 2005, Zwane Mwaikambo wrote:
> On Thu, 11 Aug 2005, Steven Rostedt wrote:
> > On Thu, 2005-08-11 at 13:46 -0400, linux-os (Dick Johnson) wrote:
> > int is a call to either an interrupt or exception procedure. 0x80 is
> > setup in Linux to be a trap and not an interrupt vector. So it
On Thu, 2005-08-11 at 22:04 -0700, Jeff Carr wrote:
> [EMAIL PROTECTED]:~# dpkg -s libc6-i686
> ...
OK, this explains it :-)
# dpkg -s libc-i686
Package `libc-i686' is not installed and no info is available.
# dpkg -s libc6
Package: libc6
Status: install ok installed
Priority: required
Section:
On Thu, 2005-08-11 at 22:04 -0700, Jeff Carr wrote:
> But are you using libc6-i686? That enables NPTL. Perhaps the behavior
> difference is there? I'm surprised int 80 doesn't really cause an
> interrupt; it doesn't jump to the appropriate place in the x86 vector
> table? Interesting.
int 80 does
On 8/12/05, Jeff Carr <[EMAIL PROTECTED]> wrote:
> On 08/11/2005 10:18 AM, Steven Rostedt wrote:
>
> > It's vanilla 2.6.12-rc3 + Ingo's RT V0.7.46-02-rs-0.4 + some of my own
> > customizations. But I never touched the sysentry stuff and with a few
> > printks I see it is being initialized.
> >
>
On 08/11/2005 10:18 AM, Steven Rostedt wrote:
> It's vanilla 2.6.12-rc3 + Ingo's RT V0.7.46-02-rs-0.4 + some of my own
> customizations. But I never touched the sysentry stuff and with a few
> printks I see it is being initialized.
>
>>Also glibc support.
>
> I'm using Debian unstable with a re
On Thu, 11 Aug 2005, Steven Rostedt wrote:
> On Thu, 2005-08-11 at 15:41 +0200, Bodo Eggert wrote:
> > According to my documentation it isn't. A software interrupt is a far call
> > with an extra pushf, and a hardware interrupt is protected against recursion
> > by the PIC, not by an interrupt fla
On Thu, 11 Aug 2005, Steven Rostedt wrote:
> On Thu, 2005-08-11 at 13:46 -0400, linux-os (Dick Johnson) wrote:
>
> >
> > I was talking about the one who had the glibc support to use
> > the newer system-call entry (who's name can confuse).
> >
> > You are looking at code that uses int 0x80. It'
On Thu, 2005-08-11 at 12:58 -0700, Zachary Amsden wrote:
> If you're feeling really masochistic, I've added a demonstration of how
> you can call sysenter from userspace without glibc.
Thanks Zach, this will give me something to play around with when I have
a little more spare time >8-}
-- Ste
Steven Rostedt wrote:
OK, I get the same on my machine.
On a machine that does not support sysenter, this will give you:
int $0x80
ret
The int $0x80 system calls are still fully supported by a sysenter
capable kernel, since it must run older binaries and potentially support
syscalls dur
On Thu, 2005-08-11 at 14:21 -0400, linux-os (Dick Johnson) wrote:
> I'm not sure you can stop the CPU from clearing the interrupt
> bit in EFLAGS if you execute an interrupt. The interrupt handler
> may be supported by a trap-gate, but the event has already
> occurred. The documentation I have isn
On Thu, 11 Aug 2005, Steven Rostedt wrote:
> On Thu, 2005-08-11 at 13:46 -0400, linux-os (Dick Johnson) wrote:
>
>>
>> I was talking about the one who had the glibc support to use
>> the newer system-call entry (who's name can confuse).
>>
>> You are looking at code that uses int 0x80. It's an in
On Thu, 2005-08-11 at 10:59 -0700, Zachary Amsden wrote:
>
> zach-dev2:~ $ ldd /bin/ls
> linux-gate.so.1 => (0xe000)
OHHH! So THAT is what linux-gate is used for! Thanks, I've been really
confused by that.
>
> This is the vsyscall entry point, which gets linked by ld into all
> pr
On Thu, 2005-08-11 at 13:46 -0400, linux-os (Dick Johnson) wrote:
>
> I was talking about the one who had the glibc support to use
> the newer system-call entry (who's name can confuse).
>
> You are looking at code that uses int 0x80. It's an interrupt,
> therefore, in the kernel, once the stack
Steven Rostedt wrote:
I expect that if I had a Gentoo system that I compiled for my machine,
this would be different. But I suspect that Debian still wants to run on
my old Pentium 75MHz laptop. How would libc know to use sysenter
instead of int 0x80. It could do a test of the system, but woul
On Thu, 11 Aug 2005, Steven Rostedt wrote:
> On Thu, 2005-08-11 at 13:26 -0400, Steven Rostedt wrote:
>
>> 288fb seems to use "int 0x80" and so do all the other system calls that
>> I inspected.
>
> I expect that if I had a Gentoo system that I compiled for my machine,
> this would be different.
On Thu, 11 Aug 2005, Steven Rostedt wrote:
> On Thu, 2005-08-11 at 13:10 -0400, linux-os (Dick Johnson) wrote:
>> On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
>
>>>
>>> Also glibc support.
>>>
>>> --
>>> Coywolf Qi Hunt
>>> http://ahbl.org/~coywolf/
>>
>> Probably doesn't use int 0x80 at all.
On Thu, 2005-08-11 at 13:26 -0400, Steven Rostedt wrote:
> 288fb seems to use "int 0x80" and so do all the other system calls that
> I inspected.
I expect that if I had a Gentoo system that I compiled for my machine,
this would be different. But I suspect that Debian still wants to run on
my old
On Thu, 2005-08-11 at 13:10 -0400, linux-os (Dick Johnson) wrote:
> On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
> >>
> >
> > Also glibc support.
> >
> > --
> > Coywolf Qi Hunt
> > http://ahbl.org/~coywolf/
>
> Probably doesn't use int 0x80 at all.
$ objdump -Dhalpr /lib/libc.so.6 | egrep 'int *\
On Fri, 2005-08-12 at 00:59 +0800, Coywolf Qi Hunt wrote:
> On 8/12/05, Coywolf Qi Hunt <[EMAIL PROTECTED]> wrote:
> > On 8/12/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> >
> > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > The cpu does have sep. Is it vanilla ker
On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
> On 8/12/05, Coywolf Qi Hunt <[EMAIL PROTECTED]> wrote:
>> On 8/12/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
>>> On Thu, 2005-08-11 at 11:51 -0400, Steven Rostedt wrote:
And booted it. The system is up and running, so I really don't thin
On 8/12/05, Coywolf Qi Hunt <[EMAIL PROTECTED]> wrote:
> On 8/12/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > On Thu, 2005-08-11 at 11:51 -0400, Steven Rostedt wrote:
> > >
> > > And booted it. The system is up and running, so I really don't think
> > > that the sysenter_entry is used for sys
On 8/12/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-08-11 at 11:51 -0400, Steven Rostedt wrote:
> >
> > And booted it. The system is up and running, so I really don't think
> > that the sysenter_entry is used for system calls.
> >
> > Not so "Clear as day"!
>
> And so, looking in
On Thu, 2005-08-11 at 11:51 -0400, Steven Rostedt wrote:
>
> And booted it. The system is up and running, so I really don't think
> that the sysenter_entry is used for system calls.
>
> Not so "Clear as day"!
And so, looking into sysenter_entry, it seems that my configurations
don't seem to u
Ukil a wrote:
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.
Almost. There are two entry points, the one
On Thu, 2005-08-11 at 11:28 -0400, linux-os (Dick Johnson) wrote:
> On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
>
> > On 8/11/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> >> On Thu, 2005-08-11 at 10:04 -0400, linux-os (Dick Johnson) wrote:
> >>> Every interrupt software, or hardware, results in
On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
> On 8/11/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
>> On Thu, 2005-08-11 at 10:04 -0400, linux-os (Dick Johnson) wrote:
>>> Every interrupt software, or hardware, results in the branched
>>> procedure being executed with the interrupts OFF. That's
On Thu, 2005-08-11 at 23:13 +0800, Coywolf Qi Hunt wrote:
>
> He is RBJ, Richard B. Johnson, the LKML defacto official troll.
>
Oh, so this is "root" who almost got DaveJ fired? :)
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
On 8/11/05, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-08-11 at 10:04 -0400, linux-os (Dick Johnson) wrote:
> > Every interrupt software, or hardware, results in the branched
> > procedure being executed with the interrupts OFF. That's why
> > one of the first instructions in the kern
On Thu, 2005-08-11 at 10:04 -0400, linux-os (Dick Johnson) wrote:
> Every interrupt software, or hardware, results in the branched
> procedure being executed with the interrupts OFF. That's why
> one of the first instructions in the kernel entry for a syscall
> is 'sti' to turn them back on. Look a
On Thu, 11 Aug 2005, Bodo Eggert wrote:
> Ukil a <[EMAIL PROTECTED]> wrote:
>
>> Now I had the doubt that if the the syscall
>> implementation is very large will the scheduling and
>> other interrupts be blocked for the whole time till
>> the process returns from the ISR (because in an ISR by
>>
On Thu, 2005-08-11 at 15:41 +0200, Bodo Eggert wrote:
> According to my documentation it isn't. A software interrupt is a far call
> with an extra pushf, and a hardware interrupt is protected against recursion
> by the PIC, not by an interrupt flag.
I disagree with your definition of a system call
On Wed, 2005-08-10 at 22:39 -0700, Ukil a wrote:
> 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.
>
> N
Ukil a <[EMAIL PROTECTED]> wrote:
> Now I had the doubt that if the the syscall
> implementation is very large will the scheduling and
> other interrupts be blocked for the whole time till
> the process returns from the ISR (because in an ISR by
> default the interrupts are disabled unless sti i
On Tue, 2 Aug 2005 09:57:51 +0100 (BST),
vinay hegde <[EMAIL PROTECTED]> wrote:
>How to differentiate kernel threads from normal
>processes inside the Linux kernel code?
The Linux Kernel Debugger (ftp://oss.sgi.com/projects/kdb/download/v4.4)
distinguishes between idle tasks, sleeping system dae
On Mon, 2005-04-18 at 15:00 +0200, Gunter wrote:
> Hello
>
> I need help about scheduling. I hope i understand the basics for my
> question: An active prozess counts the remaining cpu time in jifies. By
> every timer interrupt the scheduler decrements the variable time_slice.
>
Yes, this is corr
On Sat, May 05, 2001 at 02:32:35PM +0300, Adrian Turcu wrote:
> Hi,
>
> Some times ago I configured several Linux boxes to accept console on serial.
> Nothing new, but could some one help me with pin assignments for
> a serial cable DB9-female to DB9-female. I've lost this file
> and I need help
On Thu, 15 Mar 2001, Byron Stanoszek wrote:
> I have a real picky tape drive (DLT series) that likes to be fed large chunks
> of data at once, otherwise after every 2-4KB of data it halts and rewinds
> itself because its cache for writing to the tape is empty.
>
> My best solution to this problem
On Thu, 15 Mar 2001, Byron Stanoszek wrote:
> I have a real picky tape drive (DLT series) that likes to be fed large chunks
> of data at once, otherwise after every 2-4KB of data it halts and rewinds
> itself because its cache for writing to the tape is empty.
>
> My best solution to this proble
On Fri, 23 Feb 2001, Dwayne C. Litzenberger wrote:
> I tried asking this before; never got an answer.
>
> I suggest you just spend 20 hours or so figuring out the basic structure of
> the kernel sources. It's a long run, but you'll be happy once you do.
OK, I hate to CC all these lists, but I g
I tried asking this before; never got an answer.
I suggest you just spend 20 hours or so figuring out the basic structure of
the kernel sources. It's a long run, but you'll be happy once you do.
--
Dwayne C. Litzenberger - [EMAIL PROTECTED]
- Please always Cc to me when replying to me on the
david wrote:
>
> hi i am moving from 2.2.18 to 2.4.0 i have a ide raid set but can not
> get it to run under 2.4.0
> i user mdadd / mdrun to config it. in raid-tools 0.42 but it dose not
> come up under 2.4.0 it just says unknow devices /dev/hda3 & /dev/hdc3
> but thay are thear and when i try to
92 matches
Mail list logo
