Re: [Xen-devel] Little help with blk ring

[Daniel Castro <evil.dani@xxxxxxxxx>]

On Wed, May 9, 2012 at 5:18 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Wed, 2012-05-09 at 08:54 +0100, James Harper wrote:
>> >
>> > I am writing the PV Driver front end in Seabios.
>> >
>> > Could you explain your method in a little more detail please?
>> >
>>
>> I'm not sure that my way is the best way. The existing linux pv
>> drivers should do what you want - have a look at the source. If you
>> really want to look at my code you can get it from hg and have a look.
>> It's in the xenvbd driver.
>>
>> And I think I got it backwards in a previous email. It seems that the
>> frontend writes the protocol into the xenstore, eg "x86_64-abi" for 64
>> bit.
I was not doing this, now it is written in xenstore, as Ian´s
suggestion 32-abi, yet the same problem persists...
After RING RESPONSE 0x0009a040
status:9
operation 0
id:256
This above is the content of the response. The id should be 9. If I
change the id the response status will change to the same number. Any
ideas?

Thanks,

Daniel

>
> That's right, xen/include/public/io/protocols.h defines the valid
> protocols, your frontend should publish the one it implements (probably
> x86_32-abi for a SeaBIOS driver).
>
>>  You should probably just make sure your structures are correctly laid
>> out for a 32 bit system and then write the correct protocol string
>> into the frontend when you set up communications and that should
>> ensure that it will work on all but the most ancient Xen
>> implementations.
>>
>> James
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel
>
>



-- 
+-=====---------------------------+
| +---------------------------------+ | This space intentionally blank
for notetaking.
| |   | Daniel Castro,                |
| |   | Consultant/Programmer.|
| |   | U Andes                         |
+-------------------------------------+

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel