qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ladi Prosek <lprosek@redhat.com>
To: Itamar Tal <itamar@guardicore.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Ori Aldor" <ori@guardicore.com>,
	"Sameeh Jubran" <sameeh@daynix.com>,
	"Itamar Tal" <itamar.tal4@gmail.com>,
	"Ariel Zeitlin" <ariel@guardicore.com>,
	qemu-devel@nongnu.org, "Pavel Gurvich" <pavel@guardicore.com>,
	agraf@suse.de, "Dmitry Fleytman" <dmitry@daynix.com>,
	"Yan Vugenfirer" <yan@daynix.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] add 1394 OHCI device
Date: Tue, 5 Apr 2016 09:01:27 +0200	[thread overview]
Message-ID: <CABdb736DTdhdLa-ssFEhqYPrcUgUH=cnEvT8z1YAYfcikD8Tkw@mail.gmail.com> (raw)
In-Reply-To: <CAAe70Sui6=ta-8=9+HbUEUk5iqUd8rX803i_unqK0k_T8+Vxuw@mail.gmail.com>

Thank you Sameeh & Itamar!

Peter, it looks like there are people who care about this device and
are willing to maintain it. Would it be enough to merge the patch?

CC Alexander who may be interested as well.

Thanks,
Ladi

On Mon, Apr 4, 2016 at 4:30 PM, Itamar Tal <itamar@guardicore.com> wrote:
> Hi all,
>
> That's the exactly use case we've intended for when we've wrote this patch
> and have tested it as well. On my tests the patch worked for both 32 and 64
> bit machines for Windows Server 2003, 2008 and 2012 and it seemed to be
> working just fine. I've also benchmarked it against the good old char device
> and it was superior on a scale of magnitude.
> Feel free to ask me if you encounter any issues and I'll gladly respond.
>
> Itamar,
> Guardicore
>
>
> On Mon, Apr 4, 2016 at 3:48 PM, Sameeh Jubran <sameeh@daynix.com> wrote:
>>
>> Hello All,
>>
>> I've tested windows live debugging using the Firewire device and it seems
>> to be good.
>>
>> Test case scenario:
>>      Kernel-Mode Debugging over a 1394 as detailed in:
>> https://msdn.microsoft.com/en-us/library/windows/hardware/ff556866(v=vs.85).aspx.
>>
>> Setup:
>>     Two separate VMs, both running Windows 2012 X64. One as Host VM (
>> which runs the debugger ) and the other as Target VM ( which is being
>> debugged ).
>>
>> Qemu Command line:
>>
>>     On the Host VM:
>>         -chardev socket,id=serial10,path=/tmp/debug-serial2,server,nowait
>> \
>>         -device ohci-1394,chardev=serial10,idserial10
>>
>>     On the Target VM:
>>         -chardev socket,id=serial10,path=/tmp/debug-serial2 \
>>         -device ohci-1394,chardev=serial10,idserial10
>>
>> Results:
>> I've successfully connected to the Target VM using WindbgX64 and ran basic
>> debugging functions such as "Break" and "stack trace".
>> Moreover I've successfully viewed live trace output from virtio-net driver
>> while running Iperf test and ping.
>>
>> Tested-by: Sameeh Jubran <sameeh@daynix.com>
>>
>>
>> ------ Original Message ------
>> From: "Ladi Prosek" <lprosek@redhat.com>
>> To: qemu-devel@nongnu.org
>> Cc: peter.maydell@linaro.org; "Ladi Prosek" <lprosek@redhat.com>;
>> itamar@guardicore.com; afaerber@suse.de; itamar.tal4@gmail.com
>> Sent: 3/17/2016 10:11:33 AM
>> Subject: Re: [Qemu-devel] [PATCH] add 1394 OHCI device
>>
>>> Just a friendly ping after two weeks of silence.
>>>
>>> Thanks,
>>> Ladi
>>>
>>>
>>
>

  reply	other threads:[~2016-04-05  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 17:32 [Qemu-devel] [PATCH] add 1394 OHCI device Ladi Prosek
2016-03-17  8:11 ` Ladi Prosek
2016-04-04 12:48   ` Sameeh Jubran
2016-04-04 14:30     ` Itamar Tal
2016-04-05  7:01       ` Ladi Prosek [this message]
2016-04-05  8:01         ` Peter Maydell

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='CABdb736DTdhdLa-ssFEhqYPrcUgUH=cnEvT8z1YAYfcikD8Tkw@mail.gmail.com' \
    --to=lprosek@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=ariel@guardicore.com \
    --cc=dmitry@daynix.com \
    --cc=itamar.tal4@gmail.com \
    --cc=itamar@guardicore.com \
    --cc=ori@guardicore.com \
    --cc=pavel@guardicore.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sameeh@daynix.com \
    --cc=yan@daynix.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).