Re: [Xen-devel] [PATCH] fix free of event channel in blkfront

[tgh <tianguanhua@xxxxxxxxxx>]

hi
I try to understand the code relative to blk-attach
it seems like that device_creat()->createdevice()->addStoreEntries()
,add store entry into xenstore
then backend and frontend will watch and do several related work to real
add-device in backend and frontend ,is it right? and xenstore have
watches to check the related entry ,is it right?
I am confused ,which code or function to the real adding work
I guess there is somekind watches which do it ,but I cannot find that
fucntions

I am confused about it

could you help me
Thanks in advance

Kasai Takanori 写道:
> Hi,
>
>> Now I boot the VM with the conf file
>> ...
>> disk = [ 'file:/vm/dom3.img,sda1,w' ]
>> ...
>> and then commit the commands as follows
>>
>> [root@genode012 vmcserver]# xm block-attach dom3
>> file:/vm1/template/tp1.img sda2 w
>> [root@genode012 vmcserver]# xm block-list dom3
>> Vdev BE handle state evt-ch ring-ref BE-path
>> 2049 0 0 4 6 8 /local/domain/0/backend/vbd/107/2049
>> 2050 0 0 4 8 534 /local/domain/0/backend/vbd/107/2050
>> [root@genode012 vmcserver]# xm console dom3
>>
>> [root@office2 ~]# cat /proc/diskstats
>> ...
>>
>> 8 2 sda2 0 0 0 0 0 0 0 0 0 0 0
>
> The block-attach command seems to have succeeded.
> It can be confirmed that sda2 is attached.
>
> It can confirm the content if the mount is done.
> # mount /dev/sda2 /mnt
> # ls /mnt
>
>
>> [root@office2 ~]# df -h
>> Filesystem /dev/sda1 5.8G 4.0G 1.5G 73% /
>> none 128M 0 128M 0% /dev/shm
>>
>> what do I do wrong? How should I make it ?
>> I am really confused with it
>
> If the mount is done, it comes to see it.
> If it is recognized when starting, the block-attach command should not
> be used.
> Then, it is necessary to define two disks by configuration file.
> When starting, automatic mount will be able to be done if it set to
> /etc/fstab
> as well as Native Linux.
>
> Best Regards,
>
> -- 
> Takanori Kasai
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel