qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aditya Gupta <adityag@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, Nicholas Piggin <npiggin@gmail.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>,
	Sourabh Jain <sourabhjain@linux.ibm.com>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH v3 8/8] tests/functional: Add test for fadump in PSeries
Date: Mon, 17 Mar 2025 23:04:44 +0530	[thread overview]
Message-ID: <739b2170-ab00-4ee3-9d58-c3049d3cad5c@linux.ibm.com> (raw)
In-Reply-To: <8c5b08fb-de96-410d-9490-3e971f914c43@redhat.com>

On 17/03/25 12:30, Thomas Huth wrote:

> On 17/03/2025 07.51, Aditya Gupta wrote:
>> Hi Thomas,
>>
>> <...snip...>
>>>> +    def test_fadump_pseries_kvm(self):
>>>> +        """
>>>> +        Test Fadump in PSeries with KVM accel
>>>> +        """
>>>> +        self.do_test_fadump(is_kvm=True, is_powernv=False)
>>>> +
>>>> +if __name__ == '__main__':
>>>> +    if os.getenv("DEBUG"):
>>>> +        logging.basicConfig(level=logging.DEBUG)
>>>
>>> The setUp function in QemuSystemTest already sets the log level to 
>>> DEBUG, so this should not be necessary?
>>>
>> I did that to see the QEMU VM booting logs. I see in QemuSystemTest, 
>> it sets the log level of some loggers to DEBUG, don't know if it's 
>> the same, as I didn't see the boot logs during testing (also, in 
>> QemuSystemTest, we are setting specific loggers to DEBUG, while I did 
>> .basicConfig to DEBUG which I think is like a global debug level 
>> setting)
>>
>> How do I get the system booting logs in `make check` ? I didn't find 
>> it in the docs.
>
> The log files should get written to 
> tests/functional/ppc64/test_ppc64_fadump.* - main log file is 
> base.log, and the console output should go into console.log. Can you 
> spot there the information you were looking for?
Yes, found them, thanks !

For me, the full path was 
'<QEMU_SRC>/build/test_ppc64_fadump.QEMUFadump.test_fadump_pseries/console.log'


>
> Anyway, that information is missing in the docs indeed ... I'll try to 
> come up with a patch when I got some spare time for it.
>

Thanks, also while you make change can you also add the 'build/' folder 
at start of the path you mentioned. That might be good, I was searching 
for the files in <QEMU_SRC>/tests/functional directory.


Thanks,

- Aditya G

>  Thomas
>


      reply	other threads:[~2025-03-17 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15  6:46 [PATCH v3 0/8] Implement Firmware Assisted Dump for PSeries Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 1/8] hw/ppc: Implement skeleton code for fadump in PSeries Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 2/8] hw/ppc: Implement fadump register command Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 3/8] hw/ppc: Trigger Fadump boot if fadump is registered Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 4/8] hw/ppc: Preserve memory regions registered for fadump Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 5/8] hw/ppc: Implement saving CPU state in Fadump Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 6/8] hw/ppc: Pass dump-sizes property for fadump in device tree Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 7/8] hw/ppc: Enable fadump for PSeries Aditya Gupta
2025-03-15  6:46 ` [PATCH v3 8/8] tests/functional: Add test for fadump in PSeries Aditya Gupta
2025-03-17  6:25   ` Thomas Huth
2025-03-17  6:51     ` Aditya Gupta
2025-03-17  7:00       ` Thomas Huth
2025-03-17 17:34         ` Aditya Gupta [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=739b2170-ab00-4ee3-9d58-c3049d3cad5c@linux.ibm.com \
    --to=adityag@linux.ibm.com \
    --cc=danielhb413@gmail.com \
    --cc=harshpb@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sourabhjain@linux.ibm.com \
    --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).