From: Amos Kong <akong@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: amit.shah@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] virtio-rng: fix stuck in catting hwrng attributes
Date: Sun, 14 Sep 2014 10:25:53 +0800 [thread overview]
Message-ID: <20140914022553.GC1032@zen.redhat.com> (raw)
In-Reply-To: <20140914011208.GA1032@zen.redhat.com>
On Sun, Sep 14, 2014 at 09:12:08AM +0800, Amos Kong wrote:
...
> > > > diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
> > > > index c591d7e..b5d1b6f 100644
> > > > --- a/drivers/char/hw_random/core.c
> > > > +++ b/drivers/char/hw_random/core.c
> > > > @@ -195,8 +195,7 @@ static ssize_t rng_dev_read(struct file *filp, char __user *buf,
> > > >
> > > > mutex_unlock(&rng_mutex);
> > > >
> > > > - if (need_resched())
> > > > - schedule_timeout_interruptible(1);
> > > > + schedule_timeout_interruptible(10);
Problem only occurred in non-smp guest, we can improve it to:
if(!is_smp())
schedule_timeout_interruptible(10);
is_smp() is only available for arm arch, we need a general one.
> > > >
> > > > if (signal_pending(current)) {
> > > > err = -ERESTARTSYS;
> > > > --
--
Amos.
next prev parent reply other threads:[~2014-09-14 2:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 9:07 [PATCH 0/2] fix stuck in catting hwrng attributes Amos Kong
2014-09-10 9:07 ` [PATCH 1/2] virtio-rng cleanup: move some code out of mutex protection Amos Kong
2014-09-11 6:07 ` Amit Shah
2014-09-10 9:07 ` [PATCH 2/2] virtio-rng: fix stuck in catting hwrng attributes Amos Kong
2014-09-11 6:08 ` Amit Shah
2014-09-14 1:16 ` Amos Kong
2014-09-11 11:38 ` Rusty Russell
2014-09-13 17:12 ` Amos Kong
2014-09-14 1:12 ` Amos Kong
2014-09-14 2:25 ` Amos Kong [this message]
2014-09-15 16:48 ` Radim Krčmář
2014-09-16 0:50 ` Amos Kong
2014-09-16 15:35 ` Rusty Russell
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=20140914022553.GC1032@zen.redhat.com \
--to=akong@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/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).