public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	mttcg@greensocs.com, mark.burton@greensocs.com,
	fred.konrad@greensocs.com, a.spyridakis@virtualopensystems.com,
	kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests RFC PATCH] arm/tlbflush.c: TLB flushing torture test [DEV]
Date: Wed, 29 Jul 2015 16:36:30 +0200	[thread overview]
Message-ID: <20150729143630.GD3722@hawk.localdomain> (raw)
In-Reply-To: <55B8DC23.5040007@redhat.com>

On Wed, Jul 29, 2015 at 03:58:59PM +0200, Paolo Bonzini wrote:
> 
> 
> On 27/07/2015 09:54, Andrew Jones wrote:
> > Also, please rename to tlbflush-test.c to differentiate it
> > from an implementation of tlbflush support, and to make
> > the standalone test name (if we commit those patches) more
> > descriptive.
> 
> I disagree here.  Support code would go in lib/arm.

Generally yes, and for arm, so far yes, but not always. In x86 we
have kvmclock.c (support) vs. kvmclock_test.c (the test). And powerpc
will have a support C file in powerpc vs. lib/powerpc as well, as I
feel it fits better there, since it's really part of cstart.

But that said, I'm not overly opposed to dropping -test from the
common case, only using it when necessary. We can also append -test
for standalone test names later, if we want to.

Thanks,
drew

      reply	other threads:[~2015-07-29 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 13:25 [kvm-unit-tests RFC PATCH] arm/tlbflush.c: TLB flushing torture test [DEV] Alex Bennée
2015-07-27  7:54 ` Andrew Jones
2015-07-27  9:07   ` Alex Bennée
2015-07-27 10:32     ` Andrew Jones
2015-07-29 13:58   ` Paolo Bonzini
2015-07-29 14:36     ` Andrew Jones [this message]

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=20150729143630.GD3722@hawk.localdomain \
    --to=drjones@redhat.com \
    --cc=a.spyridakis@virtualopensystems.com \
    --cc=alex.bennee@linaro.org \
    --cc=fred.konrad@greensocs.com \
    --cc=kvm@vger.kernel.org \
    --cc=mark.burton@greensocs.com \
    --cc=mttcg@greensocs.com \
    --cc=pbonzini@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