Il 04/10/2012 10:02, Peter Maydell ha scritto:
> On 4 October 2012 04:49, Lucas Meneghel Rodrigues wrote:
>> Add a test device which supports the kvmctl ioports,
>> so one can run the KVM unittest suite [1].
>>
>> Usage:
>>
>> qemu -device testdev
>>
>> 1) Removed port 0xf1, since now kvm-unit-tes
On 4 October 2012 04:49, Lucas Meneghel Rodrigues wrote:
> Add a test device which supports the kvmctl ioports,
> so one can run the KVM unittest suite [1].
>
> Usage:
>
> qemu -device testdev
>
> 1) Removed port 0xf1, since now kvm-unit-tests use
>serial
>
> 2) Removed exit code port 0xf4, si
Il 04/10/2012 05:49, Lucas Meneghel Rodrigues ha scritto:
> Add a test device which supports the kvmctl ioports,
> so one can run the KVM unittest suite [1].
>
> Usage:
>
> qemu -device testdev
>
> 1) Removed port 0xf1, since now kvm-unit-tests use
>serial
>
> 2) Removed exit code port 0xf4
On 10/04/2012 12:49 AM, Lucas Meneghel Rodrigues wrote:
Add a test device which supports the kvmctl ioports,
so one can run the KVM unittest suite [1].
Usage:
qemu -device testdev
1) Removed port 0xf1, since now kvm-unit-tests use
serial
2) Removed exit code port 0xf4, since that can be
Add a test device which supports the kvmctl ioports,
so one can run the KVM unittest suite [1].
Usage:
qemu -device testdev
1) Removed port 0xf1, since now kvm-unit-tests use
serial
2) Removed exit code port 0xf4, since that can be
replaced by
-device isa-debugexit,iobase=0xf4,access-siz
On 08/31/2011 11:06 PM, Lucas Meneghel Rodrigues wrote:
+CharDriverState *chr;
I think it's unused, no?
Paolo
On 2011-08-31 23:06, Lucas Meneghel Rodrigues wrote:
> Add a test device which supports the kvmctl ioports,
> for running the KVM test suite.
>
> Usage:
>
> qemu
> -chardev file,path=/log/file/some/where,id=testlog
> -device pc-testdev,chardev=testlog
>
> lmr: I've tried to address t
On Wed, Aug 31, 2011 at 06:06:09PM -0300, Lucas Meneghel Rodrigues wrote:
> Add a test device which supports the kvmctl ioports,
> for running the KVM test suite.
>
> Usage:
>
> qemu
> -chardev file,path=/log/file/some/where,id=testlog
> -device pc-testdev,chardev=testlog
>
> lmr: I'
Add a test device which supports the kvmctl ioports,
for running the KVM test suite.
Usage:
qemu
-chardev file,path=/log/file/some/where,id=testlog
-device pc-testdev,chardev=testlog
lmr: I've tried to address the comments made by the
reviewers, but I probably left out some things. P
Blue Swirl writes:
> On Tue, Aug 30, 2011 at 7:36 PM, Lluís wrote:
>> Blue Swirl writes:
>>
>>> Even better, taking the instrumentation approach, could the test
>>> device be left out completely, just use guest invisible methods (like
>>> watchpoints) to interact with the guest?
>>
>> I don't g
On Tue, Aug 30, 2011 at 7:36 PM, Lluís wrote:
> Blue Swirl writes:
>
>> Even better, taking the instrumentation approach, could the test
>> device be left out completely, just use guest invisible methods (like
>> watchpoints) to interact with the guest?
>
> I don't get it. Sorry but I've not been
Blue Swirl writes:
> Even better, taking the instrumentation approach, could the test
> device be left out completely, just use guest invisible methods (like
> watchpoints) to interact with the guest?
I don't get it. Sorry but I've not been closely following the thread,
and a quick look at it gav
On Mon, Aug 29, 2011 at 5:57 AM, Avi Kivity wrote:
> On 08/27/2011 07:22 PM, Blue Swirl wrote:
>>
>> > +
>> > +static void test_device_irq_line(void *opaque, uint32_t addr, uint32_t
>> > data)
>> > +{
>> > + qemu_set_irq(isa_get_irq(addr - 0x2000), !!data);
>>
>> Where does 0x2000 come from
On 08/26/2011 06:22 PM, Anthony Liguori wrote:
On 08/26/2011 03:04 PM, Lucas Meneghel Rodrigues wrote:
Add a test device which supports the kvmctl ioports,
for running the KVM test suite. This is a straight
port from the latest version of the test device present
on qemu-kvm, using the APIs curre
On 08/27/2011 07:22 PM, Blue Swirl wrote:
> +
> +static void test_device_irq_line(void *opaque, uint32_t addr, uint32_t data)
> +{
> +qemu_set_irq(isa_get_irq(addr - 0x2000), !!data);
Where does 0x2000 come from?
The base address of this range.
> +
> +static uint32_t test_iomem_rea
On 08/27/2011 01:26 AM, Jan Kiszka wrote:
> +
> +static void test_device_irq_line(void *opaque, uint32_t addr, uint32_t data)
> +{
> +qemu_set_irq(isa_get_irq(addr - 0x2000), !!data);
Note that qemu-kvm retrieves (due to a hack) GSIs via isa_get_irq while
QEMU is and will remain confined
On 08/27/2011 01:07 PM, Edgar E. Iglesias wrote:
> >+
> >+static ISADeviceInfo testdev_info = {
> >+.qdev.name = "testdev",
> >+.qdev.size = sizeof(struct testdev),
> >+.init = init_test_device,
> >+.qdev.props = (Property[]) {
> >+DEFINE_PROP_CHR("chardev",
On 08/27/2011 12:22 AM, Anthony Liguori wrote:
I think I posted patches at some point for kvm unittests to use a
standard UART. Was there any reason not to do use a UART?
No.
+static void test_device_exit(void *opaque, uint32_t addr, uint32_t
data)
+{
+exit(data);
+}
Port 501 can
On Sat, Aug 27, 2011 at 10:07 AM, Edgar E. Iglesias
wrote:
> On Fri, Aug 26, 2011 at 04:22:22PM -0500, Anthony Liguori wrote:
>> On 08/26/2011 03:04 PM, Lucas Meneghel Rodrigues wrote:
>> >Add a test device which supports the kvmctl ioports,
>> >for running the KVM test suite. This is a straight
>
On Fri, Aug 26, 2011 at 8:04 PM, Lucas Meneghel Rodrigues
wrote:
> Add a test device which supports the kvmctl ioports,
> for running the KVM test suite. This is a straight
> port from the latest version of the test device present
> on qemu-kvm, using the APIs currently in use by qemu.
Or rather
On Fri, Aug 26, 2011 at 04:22:22PM -0500, Anthony Liguori wrote:
> On 08/26/2011 03:04 PM, Lucas Meneghel Rodrigues wrote:
> >Add a test device which supports the kvmctl ioports,
> >for running the KVM test suite. This is a straight
> >port from the latest version of the test device present
> >on q
On 2011-08-26 22:04, Lucas Meneghel Rodrigues wrote:
> Add a test device which supports the kvmctl ioports,
> for running the KVM test suite. This is a straight
> port from the latest version of the test device present
> on qemu-kvm, using the APIs currently in use by qemu.
>
> With this we aim fo
On 08/26/2011 03:04 PM, Lucas Meneghel Rodrigues wrote:
Add a test device which supports the kvmctl ioports,
for running the KVM test suite. This is a straight
port from the latest version of the test device present
on qemu-kvm, using the APIs currently in use by qemu.
With this we aim for daily
Add a test device which supports the kvmctl ioports,
for running the KVM test suite. This is a straight
port from the latest version of the test device present
on qemu-kvm, using the APIs currently in use by qemu.
With this we aim for daily execution of
the KVM unittests to capture any problems wi
24 matches
Mail list logo
