All of lore.kernel.org
 help / color / mirror / Atom feed
From: 赵小强 <zxq_yx_007@163.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Chen Fan <chen.fan.fnst@cn.fujitsu.com>,
	pbonzini@redhat.com, qemu-devel@nongnu.org, aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCH v2 2/4] apic: QOM'ify apic & icc_bus
Date: Fri, 29 Nov 2013 13:29:51 +0800	[thread overview]
Message-ID: <5298264F.6030102@163.com> (raw)
In-Reply-To: <52980E7E.4070302@suse.de>

于 11/29/2013 11:48 AM, Andreas Färber 写道:
> Am 29.11.2013 02:26, schrieb 赵小强:
>> 于 11/12/2013 10:52 PM, Andreas Färber 写道:
>>> it would be nice if you could check whether these
>>> devices (the non-KVM versions at least) are covered by make check. For
>>> ICC bus I am certain that it is.
>>    1. Does "make check" mean the build target in the Makefile ?
> Yes, in particular the make check-qtest target (check-qtest-x86_64).
>
>>   if it
>> is, I can not find anything about "icc_bus" under "tests" directory.  Or
>> you refer to something else?
> IIUC there is no strict need for an icc_bus-test.c because any test
> using -M pc (or default for i386 or x86_64) is implicitly using icc_bus
> and I don't recall any MMIO or similar implementation for ICC. It was
> just a hot-pluggable version of SysBus. My question was, does this
> implicit testing apply to the other devices touched here as well or not.
>
>>    2. What does "enable the *APIC devices and have the realize functions
>> actually exercised?" mean?
> It may mean for instance, add printfs (or assertions or breakpoints or
> trace points in core QOM code...) to the initialization code of those
> devices, run make followed by make check to see if all of them show up.
> If not, add apic-test.c, ioapic-test.c etc. using whatever -device or
> -cpu command lines necessary to trigger the printfs - and then obviously
> drop any debug printfs agains. But if I knew the answer already I
> wouldn't ask you to investigate. :)
>
> What I am not asking for is functional tests for registers or whatever -
> you did not write that code, you should just assure that your realize
> refactorings do not break device initialization accidentally.
>
> If you do find time to work on this and find that some non-KVM device is
> not covered: I was going to split off icc_bus into its own patch from 2/4.
>
> Regards,
> Andreas
>
Ok, got it !

  reply	other threads:[~2013-11-29  5:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  7:55 [Qemu-devel] [PATCH v2 0/4] QOM'ify apic and ioapic xiaoqiang zhao
2013-11-05  7:55 ` [Qemu-devel] [PATCH v2 1/4] apic: Cleanup for QOM'ify xiaoqiang zhao
2013-11-05  7:55 ` [Qemu-devel] [PATCH v2 2/4] apic: QOM'ify apic & icc_bus xiaoqiang zhao
2013-11-05  8:25   ` Chen Fan
2013-11-05  8:51     ` 赵小强
2013-11-11  3:58       ` 赵小强
2013-11-12  1:28         ` Chen Fan
2013-11-12  1:54           ` 赵小强
2013-11-12  3:02             ` Chen Fan
2013-11-12  3:11               ` 赵小强
2013-11-12 16:41               ` Andreas Färber
2013-11-13  8:47                 ` Chen Fan
2013-11-12 16:20           ` Andreas Färber
2013-11-12 14:52         ` Andreas Färber
2013-11-13  6:06           ` 赵小强
2013-11-29  1:26             ` 赵小强
2013-11-29  3:48               ` Andreas Färber
2013-11-29  5:29                 ` 赵小强 [this message]
2013-11-29  7:22                 ` 赵小强
2013-11-05  7:55 ` [Qemu-devel] [PATCH v2 3/4] ioapic: Cleanup for QOM'ify xiaoqiang zhao
2013-11-05  7:55 ` [Qemu-devel] [PATCH v2 4/4] ioapic: QOM'ify ioapic xiaoqiang zhao
  -- strict thread matches above, loose matches on Subject: below --
2013-11-05  8:16 [Qemu-devel] [PATCH v2 0/4] QOM'ify apic and ioapic xiaoqiang zhao
2013-11-05  8:16 ` [Qemu-devel] [PATCH v2 2/4] apic: QOM'ify apic & icc_bus xiaoqiang zhao
2013-11-05  7:53 [Qemu-devel] [PATCH v2 0/4] QOM'ify apic and ioapic xiaoqiang zhao
2013-11-05  7:53 ` [Qemu-devel] [PATCH v2 2/4] apic: QOM'ify apic & icc_bus xiaoqiang zhao

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=5298264F.6030102@163.com \
    --to=zxq_yx_007@163.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=chen.fan.fnst@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.