linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Mc Guire <der.herr@hofr.at>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Nicholas Mc Guire <hofrat@osadl.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux390@de.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] s390/sclp: pass timeout as HZ independent value
Date: Fri, 29 May 2015 16:16:46 +0200	[thread overview]
Message-ID: <20150529141646.GA13956@opentech.at> (raw)
In-Reply-To: <20150529140151.2846c257@holzheu>

On Fri, 29 May 2015, Michael Holzheu wrote:

> On Fri, 29 May 2015 13:49:36 +0200
> Nicholas Mc Guire <der.herr@hofr.at> wrote:
> 
> > On Fri, 29 May 2015, Heiko Carstens wrote:
> > 
> > > On Fri, May 29, 2015 at 11:51:54AM +0200, Nicholas Mc Guire wrote:
> > > > On Fri, 29 May 2015, Heiko Carstens wrote:
> > > > > Yes, the orginal code seems to be broken. Since I've no idea what the intended
> > > > > timeout value should be, let's simply ask Michael, who wrote this code eight
> > > > > years ago ;)
> > > > > While these lines get touched anyway, it would make sense to use
> > > > > schedule_timeout_interruptible() instead, and get rid of set_current_state().
> > > > >
> > > > Well that is not really equivalent
> > > > schedule_timeout_interruptible() is doing
> > > > __set_current_state not set_current_state
> > > > so that would drop the mb() and no WRITE_ONCE()
> > > 
> > > And how does that matter in this case?
> > >
> > I do not know - did not look into it - in any case
> > its not a 1:1 API consolidation that all I wanted to point out
> > before changing anything.
> 
> I agree, 1:1 consolidation is better here.
> 
> But I would like to remove the SDIAS_SLEEP_TICKS define and just
> use HZ / 2 in schedule_timeout(). Could you please resend the
> updated patch? We will then add it to our tree.
>
will do that.

I was compile testing with x86_64-gcc-4.6.3-nolibc_s390x-linux.tar.bz2 
https://www.kernel.org/pub/tools/crosstool/
but that fails for all of the available defconfigs in arch/s390/configs
would you have a pointer to a toolchain that can be used for compile testing ?

thx!
hofrat

  reply	other threads:[~2015-05-29 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 17:04 [PATCH RFC] s390/sclp: pass timeout as HZ independent value Nicholas Mc Guire
2015-05-29  9:07 ` Heiko Carstens
2015-05-29  9:51   ` Nicholas Mc Guire
2015-05-29 10:35     ` Heiko Carstens
2015-05-29 11:49       ` Nicholas Mc Guire
2015-05-29 12:01         ` Michael Holzheu
2015-05-29 14:16           ` Nicholas Mc Guire [this message]
2015-05-29 14:36             ` Heiko Carstens
2015-05-29 14:43               ` Nicholas Mc Guire

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=20150529141646.GA13956@opentech.at \
    --to=der.herr@hofr.at \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hofrat@osadl.org \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    /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).