From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
jkosina@suse.cz
Subject: Re: [PATCH REPOST] Run IST traps from user mode preemptive on process stack
Date: Tue, 11 Mar 2008 14:58:30 +0100 [thread overview]
Message-ID: <c4e36d110803110658k276c5c63x2d3703b4741a4d05@mail.gmail.com> (raw)
In-Reply-To: <20080311132616.GH18917@one.firstfloor.org>
2008/3/11, Andi Kleen <andi@firstfloor.org>:
> > I'm not sure whether this is good or bad sign - but with this patch
> > you have posted,
> > I do not have to wait in qemu for minutes to get the 'busy-loop' - I
> > get the exact same loop almost instantly when I start disk read of LV
> > partition and running my simple module insertion testcase.
>
>
> Hmm, my fix was intended to fix a gdb problem. Or rather the gdb
> problem was already fixed by disabling some functionality and with
> this patch the functionality would be reenabled again.
>
> If it fixed a qemu problem too that's great but was unintended
> on my part. In fact it is a little worrying because there should
> be no user visible change. Can you double check by unapply/test/reapply/test
> the patch really makes a difference?
I've not said it has 'fixed' my problem - I said it has exposed the
problem much faster.
But now when I've made a double test - I think I was wrong - I've been
probably judging too fast and its also probably depending on the
sunlight position, but now I can see that even with recent git kernel
without your patch I get the busy loop pretty quick :(.
> > > This patch changes these traps instead to always switch
> > > to the process stack when the trap originated from user mode.
> > > For kernel traps it keeps running non preemptive on the IST stack
> > > because that is much safer (e.g. to still get nmi watchdog events
> > > out even when the process stack is corrupted)
> > >
> >
> > So what should I check to get fixed my problem in qemu ?
>
>
> I don't know. Someone has to debug it.
But who :) ?
Zdenek
prev parent reply other threads:[~2008-03-11 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 1:24 [PATCH REPOST] Run IST traps from user mode preemptive on process stack Andi Kleen
2008-03-11 12:03 ` Zdenek Kabelac
2008-03-11 13:26 ` Andi Kleen
2008-03-11 13:58 ` Zdenek Kabelac [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e36d110803110658k276c5c63x2d3703b4741a4d05@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=andi@firstfloor.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).