From: Jeff Dike <jdike@addtoit.com>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] UML utrace support, step 1
Date: Fri, 23 Feb 2007 10:50:31 -0500 [thread overview]
Message-ID: <20070223155031.GD5198@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20070223031903.A55241800E4@magilla.sf.frob.com>
On Thu, Feb 22, 2007 at 07:19:03PM -0800, Roland McGrath wrote:
> Your replacement patch still has utrace_regset stuff in it, so it doesn't
> compile without the later patches in the series. Try applying only
> utrace-tracehook.patch from the series, then get it to build and make your
> utrace-tracehook-um.patch. Then apply only utrace-regset.patch on top of
> that, and get that building to make utrace-regset-um.patch. Then apply
> utrace-core.patch and utrace-ptrace-compat.patch to get ptrace finally
> working again and make utrace-ptrace-compat-um.patch.
Ah, I was building with all of utrace, and observing that it didn't compile
without all the bits in that patch. I'll back out the bits of utrace
I don't need yet and send another patch.
> You'll still find this insufficient when you get to biarch support (x86_64).
> At least you'll have to add another one elsewhere too, and make
> utrace_native_view refer to both.
OK, I'll deal with that when I get to it.
> Ok. We do seem to have a problem when the host has CONFIG_PREEMPT=y, which
> makes me suspect it might be a race problem that could also hit with enough
> hardware parallelism. If you get a chance to try that and can characterize
> the way it misbehaves at the level of specific ptrace/wait calls, that
> would be a great help. Otherwise I'll try to look into it when I get some
> time, but it's falling down the queue a bit since people don't seem too put
> out about it right now.
I'll turn on preempt and see what happens.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH] UML utrace support, step 1
Date: Fri, 23 Feb 2007 10:50:31 -0500 [thread overview]
Message-ID: <20070223155031.GD5198@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20070223031903.A55241800E4@magilla.sf.frob.com>
On Thu, Feb 22, 2007 at 07:19:03PM -0800, Roland McGrath wrote:
> Your replacement patch still has utrace_regset stuff in it, so it doesn't
> compile without the later patches in the series. Try applying only
> utrace-tracehook.patch from the series, then get it to build and make your
> utrace-tracehook-um.patch. Then apply only utrace-regset.patch on top of
> that, and get that building to make utrace-regset-um.patch. Then apply
> utrace-core.patch and utrace-ptrace-compat.patch to get ptrace finally
> working again and make utrace-ptrace-compat-um.patch.
Ah, I was building with all of utrace, and observing that it didn't compile
without all the bits in that patch. I'll back out the bits of utrace
I don't need yet and send another patch.
> You'll still find this insufficient when you get to biarch support (x86_64).
> At least you'll have to add another one elsewhere too, and make
> utrace_native_view refer to both.
OK, I'll deal with that when I get to it.
> Ok. We do seem to have a problem when the host has CONFIG_PREEMPT=y, which
> makes me suspect it might be a race problem that could also hit with enough
> hardware parallelism. If you get a chance to try that and can characterize
> the way it misbehaves at the level of specific ptrace/wait calls, that
> would be a great help. Otherwise I'll try to look into it when I get some
> time, but it's falling down the queue a bit since people don't seem too put
> out about it right now.
I'll turn on preempt and see what happens.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2007-02-23 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 21:21 [uml-devel] [PATCH] UML utrace support, step 1 Jeff Dike
2007-02-20 21:21 ` Jeff Dike
2007-02-21 11:12 ` [uml-devel] " Roland McGrath
2007-02-21 11:12 ` Roland McGrath
2007-02-21 18:18 ` [uml-devel] " Jeff Dike
2007-02-21 18:18 ` Jeff Dike
2007-02-23 3:19 ` [uml-devel] " Roland McGrath
2007-02-23 3:19 ` Roland McGrath
2007-02-23 15:50 ` Jeff Dike [this message]
2007-02-23 15:50 ` Jeff Dike
2007-03-05 19:21 ` [uml-devel] " Jeff Dike
2007-03-05 19:21 ` Jeff Dike
2007-03-07 8:01 ` [uml-devel] " Roland McGrath
2007-03-07 8:01 ` Roland McGrath
2007-03-16 16:25 ` [uml-devel] " Jeff Dike
2007-03-16 16:25 ` Jeff Dike
2007-03-16 23:20 ` [uml-devel] " Roland McGrath
2007-03-16 23:20 ` Roland McGrath
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=20070223155031.GD5198@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.