Re: [Qemu-devel] propose a new idea for GSOC 2014

2014-03-21 Thread Fabien Chouteau
On 03/19/2014 11:51 AM, Stefan Hajnoczi wrote:
> On Tue, Mar 18, 2014 at 9:08 PM, Daniel Smith  
> wrote:
>> I would like to propose a new idea for GSOC 2014 that I want to implement
>> for QEMU. Since QEMU are widely used for binary analysis, dynamic binary
>> code instrumentation and so on.
>> Can we provide the framework like Pin (A Dynamic Binary Instrumentation
>> Tool) for those areas in QEMU? Different from that, our framework can
>> support both user and kernel level instrumentation.
>>
>> Some potential works may include:
>> (1) Trace the instructions under a specified system call context (without
>> interrupt code);
>> (2) Integrate Xed2 for supporting disassembling. Xed2 is a very convenient
>> tool and provides bunch of APIs for disassembling.
>> (3) Support instrumentation abilities for guest OS event. For example, (1)
>> print the value of "EAX" before a specified instruction gets executed; (2)
>> print system call arguments for a certain system call.
> 

Interesting idea Daniel,

my company is using QEMU to generate execution traces that are used for
code coverage analysis. We are interested in a more generic binary
analysis integration in QEMU.

Regards,




Re: [Qemu-devel] propose a new idea for GSOC 2014

2014-03-19 Thread Stefan Hajnoczi
On Tue, Mar 18, 2014 at 9:08 PM, Daniel Smith  wrote:
> I would like to propose a new idea for GSOC 2014 that I want to implement
> for QEMU. Since QEMU are widely used for binary analysis, dynamic binary
> code instrumentation and so on.
> Can we provide the framework like Pin (A Dynamic Binary Instrumentation
> Tool) for those areas in QEMU? Different from that, our framework can
> support both user and kernel level instrumentation.
>
> Some potential works may include:
> (1) Trace the instructions under a specified system call context (without
> interrupt code);
> (2) Integrate Xed2 for supporting disassembling. Xed2 is a very convenient
> tool and provides bunch of APIs for disassembling.
> (3) Support instrumentation abilities for guest OS event. For example, (1)
> print the value of "EAX" before a specified instruction gets executed; (2)
> print system call arguments for a certain system call.

It's very late to propose a custom project idea.  I have CCed people
who may have comments about the idea in general.

Here are the steps:
1. Find a mentor (probably from among the people I CCed)
2. Flesh out the project idea, decide what is realistic to achieve
3. Submit your application at http://google-melange.com/ by 21st March 19:00 UTC

Finally, slots (funding) are limited and a project proposed late is
last in line to receive a slot.  There are already 11 ideas on the
wiki and last year we got funding for 9.

Realistically, it seems that it's too late.  I recommend you focus on
one of the project ideas already on the wiki:
http://qemu-project.org/Google_Summer_of_Code_2014

Stefan



[Qemu-devel] propose a new idea for GSOC 2014

2014-03-18 Thread Daniel Smith
Hi

I would like to propose a new idea for GSOC 2014 that I want to implement
for QEMU. Since QEMU are widely used for binary analysis, dynamic binary
code instrumentation and so on.
Can we provide the framework like Pin (A Dynamic Binary Instrumentation
Tool) for those areas in QEMU? Different from that, our framework can
support both user and kernel level instrumentation.

Some potential works may include:
(1) Trace the instructions under a specified system call context (without
interrupt code);
(2) Integrate Xed2 for supporting disassembling. Xed2 is a very convenient
tool and provides bunch of APIs for disassembling.
(3) Support instrumentation abilities for guest OS event. For example, (1)
print the value of "EAX" before a specified instruction gets executed; (2)
print system call arguments for a certain system call.

Please let me know whether you have interest for this idea.

Thanks!