From: Thomas Meyer <thomas@m3y3r.de>
To: Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Cc: "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:44:02 +0100 [thread overview]
Message-ID: <1446306242.3238.16.camel@m3y3r.de> (raw)
In-Reply-To: <5634DEAB.8090909@nod.at>
Am Samstag, den 31.10.2015, 16:30 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:24 schrieb Thomas Meyer:
> > Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
> > > Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> > > > mhh. strange. I didn't see this behaviour on my machine, but my
> > > > machine
> > > > is a rare single core system so, likely a race condition while
> > > > relaying
> > > > the timer interrupt to the userspace process.
> > >
> > > Here I can trigger it by starting UML, logging in and waiting
> > > ~5min.
> > > Then i try to run "top" --> top hangs forever.
> > >
> > > > But I'm out of ideas how this could happen!
> > >
> > > Maybe some stupid timeslice over/underflow.
> > >
> > > > what happens when you send the hanging process a SIGVTALRM
> > > > signal?
> > > > does
> > > > it proceed correctly?
> > >
> > > You mean sending SIGVTALRM to the UML host process?
> >
> > No, to the hanging userspace process, maybe the uml host process
> > did
> > receive a timer interrupt, but failed to relay this signal to the
> > correct userspace process.
>
> Well, this is not what top expects and dies.
> signal 26 (VTALRM) was caught by top, please
> see http://www.debian.org/Bugs/Reporting
>
So you did send a VTALARM in the UML system to the top process?
When yes then this was a misunderstanding! I wanted you to send a
SIGVTALRM on the uml host system to the hanging pid. does this resolve
the hang?
> The problem is within UML's scheduler it does not wake top
> after the nanosleep() expires.
> Maybe the new clock is too imprecise, dunno.
>
> Thanks,
> //richard
>
> ---------------------------------------------------------------------
> ---------
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
------------------------------------------------------------------------------
_______________________________________________
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:44 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
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 [this message]
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=1446306242.3238.16.camel@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=anton.ivanov@kot-begemot.co.uk \
--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