kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, thuth@redhat.com, borntraeger@de.ibm.com,
	linux-s390@vger.kernel.org, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 7/9] s390x: smp: Remove unneeded cpu loops
Date: Tue, 21 Jan 2020 13:59:11 +0100	[thread overview]
Message-ID: <20200121135911.4d41c418.cohuck@redhat.com> (raw)
In-Reply-To: <f0f17e60-29b6-12b1-6692-5da745cbe60a@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]

On Tue, 21 Jan 2020 13:46:51 +0100
Janosch Frank <frankja@linux.ibm.com> wrote:

> On 1/20/20 5:11 PM, Cornelia Huck wrote:
> > On Mon, 20 Jan 2020 15:41:52 +0100
> > Janosch Frank <frankja@linux.ibm.com> wrote:
> >   
> >> On 1/20/20 12:29 PM, Cornelia Huck wrote:  
> >>> On Fri, 17 Jan 2020 05:46:38 -0500
> >>> Janosch Frank <frankja@linux.ibm.com> wrote:
> >>>     
> >>>> Now that we have a loop which is executed after we return from the
> >>>> main function of a secondary cpu, we can remove the surplus loops.
> >>>>
> >>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> >>>> ---
> >>>>  s390x/smp.c | 8 +-------
> >>>>  1 file changed, 1 insertion(+), 7 deletions(-)
> >>>>
> >>>> diff --git a/s390x/smp.c b/s390x/smp.c
> >>>> index 555ed72..c12a3db 100644
> >>>> --- a/s390x/smp.c
> >>>> +++ b/s390x/smp.c
> >>>> @@ -29,15 +29,9 @@ static void wait_for_flag(void)
> >>>>  	}
> >>>>  }
> >>>>  
> >>>> -static void cpu_loop(void)
> >>>> -{
> >>>> -	for (;;) {}
> >>>> -}
> >>>> -
> >>>>  static void test_func(void)
> >>>>  {
> >>>>  	testflag = 1;
> >>>> -	cpu_loop();
> >>>>  }
> >>>>  
> >>>>  static void test_start(void)
> >>>> @@ -234,7 +228,7 @@ int main(void)
> >>>>  
> >>>>  	/* Setting up the cpu to give it a stack and lowcore */
> >>>>  	psw.mask = extract_psw_mask();
> >>>> -	psw.addr = (unsigned long)cpu_loop;
> >>>> +	psw.addr = (unsigned long)test_func;    
> >>>
> >>> Before, you did not set testflag here... intended change?    
> >>
> >> Yes
> >> It is set to 0 before the first test, so it shouldn't matter.  
> > 
> > Hm... I got a bit lost in all those changes, so I checked your branch
> > on github, and I don't see it being set to 0 before test_start() is
> > called?  
> 
> Well, that's because test_start doesn't care about the flag.

But I see a wait_for_flag() in there? What am I missing?

> ecall and emcall are the first users, and they set it to 0 before using it.
> 
> >   
> >>  
> >>>     
> >>>>  	smp_cpu_setup(1, psw);
> >>>>  	smp_cpu_stop(1);
> >>>>      
> >>>     
> >>
> >>  
> >   
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-01-21 12:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 10:46 [kvm-unit-tests PATCH v3 0/9] s390x: smp: Improve smp code and reset checks Janosch Frank
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 1/9] s390x: smp: Cleanup smp.c Janosch Frank
2020-01-20 12:02   ` David Hildenbrand
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 2/9] s390x: smp: Only use smp_cpu_setup once Janosch Frank
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 3/9] s390x: Add cpu id to interrupt error prints Janosch Frank
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 4/9] s390x: smp: Rework cpu start and active tracking Janosch Frank
2020-01-20 12:06   ` David Hildenbrand
2020-01-20 13:16     ` Thomas Huth
2020-01-20 13:20       ` David Hildenbrand
2020-01-20 14:47     ` Janosch Frank
2020-01-20 14:53       ` David Hildenbrand
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 5/9] s390x: smp: Wait for cpu setup to finish Janosch Frank
2020-01-20 11:04   ` Cornelia Huck
2020-01-20 12:07   ` David Hildenbrand
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 6/9] s390x: smp: Loop if secondary cpu returns into cpu setup again Janosch Frank
2020-01-20 11:27   ` Cornelia Huck
2020-01-20 12:07     ` David Hildenbrand
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 7/9] s390x: smp: Remove unneeded cpu loops Janosch Frank
2020-01-20 11:29   ` Cornelia Huck
2020-01-20 14:41     ` Janosch Frank
2020-01-20 16:11       ` Cornelia Huck
2020-01-21 12:46         ` Janosch Frank
2020-01-21 12:59           ` Cornelia Huck [this message]
2020-01-21 13:07             ` Janosch Frank
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 8/9] s390x: smp: Test all CRs on initial reset Janosch Frank
2020-01-20 11:44   ` Cornelia Huck
2020-01-20 12:10   ` David Hildenbrand
2020-01-20 14:49     ` Janosch Frank
2020-01-20 14:53       ` David Hildenbrand
2020-01-17 10:46 ` [kvm-unit-tests PATCH v3 9/9] s390x: smp: Dirty fpc before initial reset test Janosch Frank

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=20200121135911.4d41c418.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=thuth@redhat.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).