From: Thomas Meyer <thomas@m3y3r.de>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Cc: Richard Weinberger <richard@nod.at>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH v3] um: Switch clocksource to hrtimers
Date: Sat, 31 Oct 2015 16:10:32 +0100 [thread overview]
Message-ID: <1446304232.3238.8.camel@m3y3r.de> (raw)
In-Reply-To: <CAFLxGvwDXWhw+mssT4quUaRC3DFAtRAGksmV-wuYrdzLWZEa0w@mail.gmail.com>
Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
> On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
> <anton.ivanov@kot-begemot.co.uk> wrote:
> > I got the first patchset to build, it works very well on a single
> > core
> > host or with CPU pinning of the UML - the performance gain is >
> > 25%.
> >
> > However, I introduced a race somewhere along the way - it crashes
> > UML
> > reliably if you do not pin CPUs.
>
> How does the crash look like?
> I see also an issue with that patch, after UML has an uptime of a few
> minutes
> a task which does nanosleep() will never wake up.
>
> [<000000006001a29d>] __switch_to+0x53/0x82
> [<00000000602995d2>] __schedule+0x2f4/0x3f7
> [<0000000060299751>] schedule+0x7c/0x95
> [<000000006029b871>] do_nanosleep+0x8b/0x134
> [<0000000060068a41>] hrtimer_nanosleep+0xb2/0x15a
> [<0000000060068b90>] SyS_nanosleep+0xa7/0xbf
> [<000000006001d492>] handle_syscall+0x6a/0x84
> [<00000000600304a8>] userspace+0x3d8/0x463
> [<000000006001a180>] fork_handler+0x85/0x87
> [<ffffffffffffffff>] 0xffffffffffffffff
>
Hi,
is this crash/hang about the "switch clocksource to hrtimers" patch or
about the next patch that improves UBD improvements?
------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2015-10-31 15:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 8:42 [uml-devel] [PATCH v3] um: Switch clocksource to hrtimers Anton Ivanov
2015-10-25 18:46 ` Anton Ivanov
2015-10-26 10:12 ` Richard Weinberger
2015-10-29 6:23 ` Anton Ivanov
2015-10-31 13:54 ` Richard Weinberger
2015-10-31 15:10 ` Thomas Meyer [this message]
2015-10-31 15:13 ` Richard Weinberger
2015-10-31 15:16 ` Thomas Meyer
2015-10-31 15:21 ` Richard Weinberger
2015-10-31 15:24 ` Thomas Meyer
2015-10-31 15:30 ` Richard Weinberger
2015-10-31 15:44 ` Thomas Meyer
2015-10-31 16:22 ` Anton Ivanov
2015-10-31 19:08 ` Richard Weinberger
2015-10-31 20:17 ` Anton Ivanov
2015-10-31 19:06 ` Richard Weinberger
2015-11-02 8:14 ` Anton Ivanov
2015-11-02 8:37 ` Richard Weinberger
2015-11-02 8:41 ` Anton Ivanov
2015-11-02 8:52 ` Richard Weinberger
2015-11-02 8:57 ` Anton Ivanov
2015-11-02 9:12 ` Richard Weinberger
2015-11-02 9:53 ` Anton Ivanov
2015-11-02 10:01 ` Richard Weinberger
2015-11-02 10:59 ` Anton Ivanov
2015-11-02 11:00 ` Anton Ivanov
2015-11-02 14:30 ` Anton Ivanov
2015-11-02 15:25 ` Richard Weinberger
2015-11-02 16:19 ` Anton Ivanov
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=1446304232.3238.8.camel@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox