Hi Andi,
Max Krasnyanskiy <[EMAIL PROTECTED]> writes:
static struct module *load_module(void __user *umod,
unsigned long len,
const char __user *uargs)
{
...
/* Now sew it into the lists so we can get lockdep and oops
Max Krasnyanskiy <[EMAIL PROTECTED]> writes:
>
> static struct module *load_module(void __user *umod,
> unsigned long len,
> const char __user *uargs)
> {
> ...
>
> /* Now sew it into the lists so we can get lockdep and
Max Krasnyanskiy [EMAIL PROTECTED] writes:
static struct module *load_module(void __user *umod,
unsigned long len,
const char __user *uargs)
{
...
/* Now sew it into the lists so we can get lockdep and oops
Hi Andi,
Max Krasnyanskiy [EMAIL PROTECTED] writes:
static struct module *load_module(void __user *umod,
unsigned long len,
const char __user *uargs)
{
...
/* Now sew it into the lists so we can get lockdep and oops
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
Max Krasnyanskiy wrote:
> Tejun Heo wrote:
>> Max Krasnyanskiy wrote:
>>> Thanks for the info. I guess I missed that from the code. In any case
>>> that seems like a pretty heavy refcounting mechanism. In a sense that
>>> every time something is loaded or unloaded entire machine freezes,
>>>
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
potentially for several milliseconds. Normally
Max Krasnyanskiy wrote:
> Thanks for the info. I guess I missed that from the code. In any case
> that seems like a pretty heavy refcounting mechanism. In a sense that
> every time something is loaded or unloaded entire machine freezes,
> potentially for several milliseconds. Normally it's not a
Hi Tejun,
Max Krasnyansky wrote:
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
potentially for several milliseconds. Normally it's not a big
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
potentially for several milliseconds. Normally
Hi Tejun,
Max Krasnyansky wrote:
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People
Max Krasnyanskiy wrote:
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
potentially for
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Tejun Heo wrote:
Max Krasnyanskiy wrote:
Thanks for the info. I guess I missed that from the code. In any case
that seems like a pretty heavy refcounting mechanism. In a sense that
every time something is loaded or unloaded entire machine freezes,
Hello, Max.
Max Krasnyansky wrote:
> I was hopping you could answer a couple of questions about module
> loading/unloading
> and the stop machine.
> There was a recent discussion on LKML about CPU isolation patches I'm working
> on.
> One of the patches makes stop machine i
Jike Song wrote:
> On 2/8/08, Max Krasnyansky <[EMAIL PROTECTED]> wrote:
>> Hi Rusty,
>>
>> I was hopping you could answer a couple of questions about module
>> loading/unloading
>> and the stop machine.
>
> I'm curious to know why it is called `stop
On 2/8/08, Max Krasnyansky <[EMAIL PROTECTED]> wrote:
> Hi Rusty,
>
> I was hopping you could answer a couple of questions about module
> loading/unloading
> and the stop machine.
I'm curious to know why it is called `stop machine', which is a queer
name without any
On 2/8/08, Max Krasnyansky [EMAIL PROTECTED] wrote:
Hi Rusty,
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
I'm curious to know why it is called `stop machine', which is a queer
name without any relationship with its function
Hello, Max.
Max Krasnyansky wrote:
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs
Max Krasnyansky wrote:
Hi Rusty,
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People
Max Krasnyansky wrote:
Hi Rusty,
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People
Hi Rusty,
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People of
course had
questions
Hi Rusty,
I was hopping you could answer a couple of questions about module
loading/unloading
and the stop machine.
There was a recent discussion on LKML about CPU isolation patches I'm working
on.
One of the patches makes stop machine ignore the isolated CPUs. People of
course had
questions
23 matches
Mail list logo
