mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: "John 'Warthog9' Hawley" <warthog9@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: ktest help
Date: Thu, 6 Apr 2017 12:49:01 -0400	[thread overview]
Message-ID: <20170406124901.0e5efe12@gandalf.local.home> (raw)
In-Reply-To: <d034a112-f58b-16b3-babb-f5528f1ee399@codeaurora.org>


I added LKML (others may want to know this too), and John, who's going
to help me maintain ktest.

On Thu, 6 Apr 2017 11:34:45 -0500
Timur Tabi <timur@codeaurora.org> wrote:

> On 04/05/2017 08:53 PM, Steven Rostedt wrote:
> >> > Why is it prompting me for the MACHINE when I've specified it in the
> >> > ktest.conf file?  
> > My answer is above. If you have other questions, feel free to ask.  
> 
> Thank you, that fixed it.  I will submit a patch that adds a note so that no
> one else makes that mistake.
> 
> Do you have any more sample kconf files?  I'm trying to get ktest to work

I have lots of kconf files. ktest is basically the only way I build my
kernels now :-)

> with my environment.  The way I boot my target is, after it's powered on,
> the system PXE boots a Grub.  From that screen, I press 'c' to get the
> command line, where I enter a command prompt and then type in "boot".  Like
> this:
> 
> grub> linux AUSB33_SDP_Linux/Image.q rootwait rw ip=dhcp root=/dev/sda2  
> rootfstype=ext4 panic=1 acpi.debug_level=2
> earlycon=pl011,0xff78ed1000,qdf2400_e44
> grub> boot  
> 
> This tftp's the kernel image (Image.q) and then boots.  I'm having
> difficulty figuring out how to implement that in ktest.
> 

Can you make a script do this? If so, then you can simply tell ktest to
call that script. See the options SWITCH_TO_TEST and SWITCH_TO_GOOD.

-- Steve

       reply	other threads:[~2017-04-06 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c2619a27-eca9-c80d-ea62-e5536ccf6ae6@codeaurora.org>
     [not found] ` <20170405215350.0c43734c@grimm.local.home>
     [not found]   ` <d034a112-f58b-16b3-babb-f5528f1ee399@codeaurora.org>
2017-04-06 16:49     ` Steven Rostedt [this message]
2017-04-06 17:01       ` Timur Tabi
2017-04-06 17:05         ` Steven Rostedt
2017-04-06 18:39           ` Timur Tabi
2017-04-06 18:50             ` Steven Rostedt
2017-04-06 18:53               ` Timur Tabi
2017-04-06 19:14                 ` Steven Rostedt

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=20170406124901.0e5efe12@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timur@codeaurora.org \
    --cc=warthog9@kernel.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

all inboxes | Powered by JetHome®