* Re: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in vmbus_bus_init()
From: Dan Carpenter @ 2011-08-30 10:29 UTC (permalink / raw)
To: Greg KH
Cc: K. Y. Srinivasan, devel, Haiyang Zhang, gregkh, linux-kernel,
virtualization
In-Reply-To: <20110829180842.GA23618@kroah.com>
> err3:
> free_irq(irq, hv_acpi_dev);
> err2:
> bus_unregister(&hv_bus);
> err1:
> hv_cleanup();
Also here is an oldbie trick. You could use multiples of ten like
err30, err20, and err10. That way if you can add more error handling
in the middle without changing the numbering. I knew my GW-BASIC
experience would come in handy one day. :)
The better way to label things is based on what happens when you get
there: err_irq, err_unregister, err_cleanup.
Some people label things based on where the goto is, but that breaks
down if there is more than one goto. It doesn't really make sense to
name the destination after the starting point.
regards,
dan carpenter
^ permalink raw reply
* Re: [PATCH 18/46] Staging: hv: storvsc: Add code to handle IDE devices using the storvsc driver
From: Dan Carpenter @ 2011-08-30 11:07 UTC (permalink / raw)
To: K. Y. Srinivasan
Cc: devel, Haiyang Zhang, gregkh, linux-kernel, virtualization
In-Reply-To: <1314469905-7058-18-git-send-email-kys@microsoft.com>
On Sat, Aug 27, 2011 at 11:31:17AM -0700, K. Y. Srinivasan wrote:
> @@ -59,6 +59,17 @@ struct storvsc_cmd_request {
> struct hv_storvsc_request request;
> };
>
> +static void storvsc_get_ide_info(struct hv_device *dev, int *target, int *path)
> +{
> + *target =
> + dev->dev_instance.b[5] << 8 | dev->dev_instance.b[4];
> +
> + *path =
> + dev->dev_instance.b[3] << 24 |
> + dev->dev_instance.b[2] << 16 |
> + dev->dev_instance.b[1] << 8 | dev->dev_instance.b[0];
> +}
> +
Does endianness matter here? It seems like *path isn't actually used
anywhere. Probably target and path should be u32 types?
regards,
dan carpenter
^ permalink raw reply
* Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: Olaf Hering @ 2011-08-30 12:48 UTC (permalink / raw)
To: K. Y. Srinivasan; +Cc: gregkh, linux-kernel, devel, virtualization
In-Reply-To: <1314469874-7017-1-git-send-email-kys@microsoft.com>
On Sat, Aug 27, K. Y. Srinivasan wrote:
> 2) Handle all block devices using the storvsc driver. I have modified
> the implementation here based on Christoph's feedback on my earlier
> implementation.
The upgrade path from hv_blkvsc to hv_storvsc is difficult.
hv_storvsc does not provide the vmbus:hv_block modalias, so mkinitrd
does not know what module to choose when mkinitrd is called in a
previous kernel (like sles11sp1).
In a guest with both SCSI and IDE controllers the IDE disks are
discovered first, so the SCSI drives will also change their names.
Thats not a problem for data partitions because they could be mounted by
UUID or LABEL in fstab.
But its difficult to adjust /boot/grub/device.map for example because
the old IDE drives do not provide an identifier. What is the best way
to make sure the rename from hd* to sd* in such config files is done
correctly? Is it safe to assume that all drives with a class_id of
32412632-86cb-44a2-9b5c50d1417354f5 are connected to IDE ports?
localhost:~ # head /sys/bus/vmbus/devices/vmbus_0_{1,2,3,10,11}/class_id
==> /sys/bus/vmbus/devices/vmbus_0_1/class_id <==
{32412632-86cb-44a2-9b5c50d1417354f5}
==> /sys/bus/vmbus/devices/vmbus_0_2/class_id <==
{32412632-86cb-44a2-9b5c50d1417354f5}
==> /sys/bus/vmbus/devices/vmbus_0_3/class_id <==
{32412632-86cb-44a2-9b5c50d1417354f5}
==> /sys/bus/vmbus/devices/vmbus_0_10/class_id <==
{ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
==> /sys/bus/vmbus/devices/vmbus_0_11/class_id <==
{ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
In my test system, the IDE drives are now discovered twice, once by
hv_storvsc and once by libata:
localhost:~ # lsscsi
[0:0:0:0] disk Msft Virtual Disk 1.0 /dev/sda
[1:0:1:0] disk Msft Virtual Disk 1.0 /dev/sdb
[2:0:1:0] disk Msft Virtual Disk 1.0 /dev/sdc
[3:0:0:0] disk Msft Virtual Disk 1.0 /dev/sdd
[3:0:0:1] disk Msft Virtual Disk 1.0 /dev/sde
[4:0:0:0] disk Msft Virtual Disk 1.0 /dev/sdf
[4:0:0:1] disk Msft Virtual Disk 1.0 /dev/sdg
[5:0:0:0] disk ATA Virtual HD 1.1. /dev/sdh
[5:0:1:0] disk ATA Virtual HD 1.1. /dev/sdi
[6:0:0:0] cd/dvd Msft Virtual CD/ROM 1.0 /dev/sr0
[6:0:1:0] disk ATA Virtual HD 1.1. /dev/sdj
localhost:~ # blkid
/dev/sda1: UUID="47aebbfb-13ee-49cc-b1e7-bc0c243fe3c0" TYPE="swap"
/dev/sda2: UUID="ed5a182b-da28-42f2-acff-5649a8fae247" TYPE="ext3"
/dev/sdh1: UUID="47aebbfb-13ee-49cc-b1e7-bc0c243fe3c0" TYPE="swap"
/dev/sdh2: UUID="ed5a182b-da28-42f2-acff-5649a8fae247" TYPE="ext3"
sda/sdh was hda.
Olaf
^ permalink raw reply
* Re: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in vmbus_bus_init()
From: Greg KH @ 2011-08-30 14:07 UTC (permalink / raw)
To: Dan Carpenter
Cc: K. Y. Srinivasan, devel, Haiyang Zhang, gregkh, linux-kernel,
virtualization
In-Reply-To: <20110830102949.GD3705@shale.localdomain>
On Tue, Aug 30, 2011 at 01:29:49PM +0300, Dan Carpenter wrote:
> > err3:
> > free_irq(irq, hv_acpi_dev);
> > err2:
> > bus_unregister(&hv_bus);
> > err1:
> > hv_cleanup();
>
> Also here is an oldbie trick. You could use multiples of ten like
> err30, err20, and err10. That way if you can add more error handling
> in the middle without changing the numbering. I knew my GW-BASIC
> experience would come in handy one day. :)
>
> The better way to label things is based on what happens when you get
> there: err_irq, err_unregister, err_cleanup.
Yes, that's the best way to do this, thanks for pointing it out.
greg k-h
^ permalink raw reply
* Re: [PATCH 10/59] Staging: hv: util: Make hv_utils a vmbus device driver
From: Dan Carpenter @ 2011-08-30 15:53 UTC (permalink / raw)
To: K. Y. Srinivasan
Cc: devel, Haiyang Zhang, gregkh, linux-kernel, virtualization
In-Reply-To: <1314290965-2698-10-git-send-email-kys@microsoft.com>
On Thu, Aug 25, 2011 at 09:48:36AM -0700, K. Y. Srinivasan wrote:
> + util_drv.driver.name = driver_name;
> +
> + return vmbus_child_driver_register(&util_drv.driver);
We should free the allocations if vmbus_child_driver_register() fails.
regards,
dan carpenter
^ permalink raw reply
* RE: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in connection.c
From: KY Srinivasan @ 2011-08-30 17:03 UTC (permalink / raw)
To: Joe Perches
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <1314514612.6852.11.camel@Joe-Laptop>
> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com]
> Sent: Sunday, August 28, 2011 2:57 AM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in
> connection.c
>
> On Sat, 2011-08-27 at 11:31 -0700, K. Y. Srinivasan wrote:
> > Fix checkpatch warnings in connection.c.
> []
> > diff --git a/drivers/staging/hv/connection.c b/drivers/staging/hv/connection.c
> []
> > @@ -220,11 +220,11 @@ static void process_chn_event(u32 relid)
> > channel = relid2channel(relid);
> >
> > spin_lock_irqsave(&channel->inbound_lock, flags);
> > - if (channel && (channel->onchannel_callback != NULL)) {
> > + if (channel && (channel->onchannel_callback != NULL))
>
> Useless test for channel or bad placement for spin_lock.
> channel has already been dereferenced by the spin_lock.
>
>
Thanks Joe. I will fix this up.
Regards,
K. Y
^ permalink raw reply
* RE: [PATCH 37/46] Staging: hv: vmbus: Check for events before messages
From: KY Srinivasan @ 2011-08-30 17:06 UTC (permalink / raw)
To: Greg KH
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <20110829180511.GA7167@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Monday, August 29, 2011 2:05 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 37/46] Staging: hv: vmbus: Check for events before
> messages
>
> On Sat, Aug 27, 2011 at 11:31:36AM -0700, K. Y. Srinivasan wrote:
> > Conform to Windows specification by checking for events before messages.
>
> What specification?
>
> Care to provide a comment in the code that you are doing this in this
> explicit order because of some rule that the hypervisor imposes on us?
I am not sure if this is documented anywhere (publicly). In talking to Windows
guys, they suggested this is the order in which it is done on Windows guests and suggested
I should do the same. I will see if there is some public documentation that specifies this.
Regards,
K. Y
>
> thanks,
>
> greg k-h
^ permalink raw reply
* RE: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in vmbus_bus_init()
From: KY Srinivasan @ 2011-08-30 17:07 UTC (permalink / raw)
To: Greg KH
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <20110829180842.GA23618@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Monday, August 29, 2011 2:09 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in
> vmbus_bus_init()
>
> On Sat, Aug 27, 2011 at 11:31:40AM -0700, K. Y. Srinivasan wrote:
> > Fix a bug in error handling in vmbus_bus_init().
> >
> > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > ---
> > drivers/staging/hv/vmbus_drv.c | 21 ++++++++++-----------
> > 1 files changed, 10 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/staging/hv/vmbus_drv.c b/drivers/staging/hv/vmbus_drv.c
> > index 02edb11..4d1b123 100644
> > --- a/drivers/staging/hv/vmbus_drv.c
> > +++ b/drivers/staging/hv/vmbus_drv.c
> > @@ -492,7 +492,7 @@ static int vmbus_bus_init(int irq)
> >
> > ret = bus_register(&hv_bus);
> > if (ret)
> > - return ret;
> > + goto err1;
> >
> > ret = request_irq(irq, vmbus_isr, IRQF_SAMPLE_RANDOM,
> > driver_name, hv_acpi_dev);
> > @@ -500,10 +500,7 @@ static int vmbus_bus_init(int irq)
> > if (ret != 0) {
> > pr_err("Unable to request IRQ %d\n",
> > irq);
> > -
> > - bus_unregister(&hv_bus);
> > -
> > - return ret;
> > + goto err2;
> > }
> >
> > vector = IRQ0_VECTOR + irq;
> > @@ -514,16 +511,18 @@ static int vmbus_bus_init(int irq)
> > */
> > on_each_cpu(hv_synic_init, (void *)&vector, 1);
> > ret = vmbus_connect();
> > - if (ret) {
> > - free_irq(irq, hv_acpi_dev);
> > - bus_unregister(&hv_bus);
> > - return ret;
> > - }
> > -
> > + if (ret)
> > + goto err3;
> >
> > vmbus_request_offers();
> >
> > return 0;
> > +
> > +err3: free_irq(irq, hv_acpi_dev);
> > +err2: bus_unregister(&hv_bus);
> > +err1: hv_cleanup();
>
> The traditional way to write this is:
>
> err3:
> free_irq(irq, hv_acpi_dev);
> err2:
> bus_unregister(&hv_bus);
> err1:
> hv_cleanup();
>
> Care to fix this up and resend it?
Will do.
Regards,
K. Y
^ permalink raw reply
* RE: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in connection.c
From: KY Srinivasan @ 2011-08-30 17:11 UTC (permalink / raw)
To: Greg KH
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <20110829180934.GB23618@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Monday, August 29, 2011 2:10 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in
> connection.c
>
> On Sat, Aug 27, 2011 at 11:31:43AM -0700, K. Y. Srinivasan wrote:
> > Fix checkpatch warnings in connection.c.
> >
> > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > ---
> > drivers/staging/hv/connection.c | 13 +++++++------
> > 1 files changed, 7 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/staging/hv/connection.c b/drivers/staging/hv/connection.c
> > index ca92ca3..9e99c04 100644
> > --- a/drivers/staging/hv/connection.c
> > +++ b/drivers/staging/hv/connection.c
> > @@ -220,11 +220,11 @@ static void process_chn_event(u32 relid)
> > channel = relid2channel(relid);
> >
> > spin_lock_irqsave(&channel->inbound_lock, flags);
> > - if (channel && (channel->onchannel_callback != NULL)) {
> > + if (channel && (channel->onchannel_callback != NULL))
> > channel->onchannel_callback(channel-
> >channel_callback_context);
> > - } else {
>
> I agree with Joe here, if channel really was NULL, you just oopsed.
>
> I'll apply this one, but please send me a follow-on one fixing this bug.
Thanks Greg. I will fix this. I got these patches out just before Hurricane Irene
hit the east coast. While we were lucky that it was not as bad as was predicted,
we lost power and we still don't have power. I have come to a public library in
a nearby town to check my email. So, my responses will be sporadic over the
next couple of days (until we get power). I will try to address the issues you
have raised as quickly as possible.
Regards,
K. Y
^ permalink raw reply
* RE: [PATCH 46/46] Staging: hv: Update the TODO file
From: KY Srinivasan @ 2011-08-30 17:13 UTC (permalink / raw)
To: Greg KH
Cc: devel@linuxdriverproject.org, Haiyang Zhang, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110829181206.GB19668@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Monday, August 29, 2011 2:12 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 46/46] Staging: hv: Update the TODO file
>
> On Sat, Aug 27, 2011 at 11:31:45AM -0700, K. Y. Srinivasan wrote:
> > Update the TODO file.
> >
> > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > ---
> > drivers/staging/hv/TODO | 24 ++++++++++++++++++++----
> > 1 files changed, 20 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/staging/hv/TODO b/drivers/staging/hv/TODO
> > index 582fd4a..23c74ed 100644
> > --- a/drivers/staging/hv/TODO
> > +++ b/drivers/staging/hv/TODO
> > @@ -1,14 +1,30 @@
> > TODO:
> > - - fix remaining checkpatch warnings and errors
> > - audit the vmbus to verify it is working properly with the
> > driver model
> > - - see if the vmbus can be merged with the other virtual busses
> > - in the kernel
> > +
> > + STATUS (July 19, 2011):
> > + All outstanding issues (known to us) with regards
> > + to conforming to Linux Driver Model have been addressed.
>
> The TODO file is not a place to have a "conversation" about what is and
> is not completed by having status reports.
>
> Let's discuss this through email, and if we all agree, then the TODO
> entries can be removed.
Ok; will do.
K. Y
>
> greg k-h
^ permalink raw reply
* RE: [PATCH 10/59] Staging: hv: util: Make hv_utils a vmbus device driver
From: KY Srinivasan @ 2011-08-30 17:14 UTC (permalink / raw)
To: Dan Carpenter
Cc: devel@linuxdriverproject.org, Haiyang Zhang, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830155323.GT3705@shale.localdomain>
> -----Original Message-----
> From: Dan Carpenter [mailto:error27@gmail.com]
> Sent: Tuesday, August 30, 2011 11:53 AM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 10/59] Staging: hv: util: Make hv_utils a vmbus device driver
>
> On Thu, Aug 25, 2011 at 09:48:36AM -0700, K. Y. Srinivasan wrote:
> > + util_drv.driver.name = driver_name;
> > +
> > + return vmbus_child_driver_register(&util_drv.driver);
>
> We should free the allocations if vmbus_child_driver_register() fails.
Thanks Dan. I will take care of this.
Regards,
K. Y
^ permalink raw reply
* RE: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: KY Srinivasan @ 2011-08-30 17:22 UTC (permalink / raw)
To: Olaf Hering
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
In-Reply-To: <20110830124856.GA17520@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Tuesday, August 30, 2011 8:49 AM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org
> Subject: Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
>
> On Sat, Aug 27, K. Y. Srinivasan wrote:
>
> > 2) Handle all block devices using the storvsc driver. I have modified
> > the implementation here based on Christoph's feedback on my earlier
> > implementation.
>
> The upgrade path from hv_blkvsc to hv_storvsc is difficult.
>
> hv_storvsc does not provide the vmbus:hv_block modalias, so mkinitrd
> does not know what module to choose when mkinitrd is called in a
> previous kernel (like sles11sp1).
>
>
> In a guest with both SCSI and IDE controllers the IDE disks are
> discovered first, so the SCSI drives will also change their names.
> Thats not a problem for data partitions because they could be mounted by
> UUID or LABEL in fstab.
> But its difficult to adjust /boot/grub/device.map for example because
> the old IDE drives do not provide an identifier. What is the best way
> to make sure the rename from hd* to sd* in such config files is done
> correctly? Is it safe to assume that all drives with a class_id of
> 32412632-86cb-44a2-9b5c50d1417354f5 are connected to IDE ports?
The class_id is invariant as we are returning the guid of the device under class_id.
So, if you see a IDE guid under class_id, you can be sure (a) it is an ide device and (b)
it is a device managed via the PV drivers.
>
> localhost:~ # head /sys/bus/vmbus/devices/vmbus_0_{1,2,3,10,11}/class_id
> ==> /sys/bus/vmbus/devices/vmbus_0_1/class_id <==
> {32412632-86cb-44a2-9b5c50d1417354f5}
>
> ==> /sys/bus/vmbus/devices/vmbus_0_2/class_id <==
> {32412632-86cb-44a2-9b5c50d1417354f5}
>
> ==> /sys/bus/vmbus/devices/vmbus_0_3/class_id <==
> {32412632-86cb-44a2-9b5c50d1417354f5}
>
> ==> /sys/bus/vmbus/devices/vmbus_0_10/class_id <==
> {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
>
> ==> /sys/bus/vmbus/devices/vmbus_0_11/class_id <==
> {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
>
>
> In my test system, the IDE drives are now discovered twice, once by
> hv_storvsc and once by libata:
This is a known (old problem). The way this was handled earlier was to have the
modprobe rules in place to setup a dependency that would force the load of the
hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
driver succeeded, we would not load the native driver. In sles11 sp1, we had a rule for
loading blkvsc. With the merge of blkvsc and storvsc, the only change we need to make
is to have storvsc in the rule (instaed of blkvsc).
Regards,
K. Y
^ permalink raw reply
* RE: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in vmbus_bus_init()
From: KY Srinivasan @ 2011-08-30 17:25 UTC (permalink / raw)
To: Greg KH, Dan Carpenter
Cc: devel@linuxdriverproject.org, Haiyang Zhang, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830140725.GA16570@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Tuesday, August 30, 2011 10:07 AM
> To: Dan Carpenter
> Cc: KY Srinivasan; devel@linuxdriverproject.org; Haiyang Zhang; gregkh@suse.de;
> linux-kernel@vger.kernel.org; virtualization@lists.osdl.org
> Subject: Re: [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in
> vmbus_bus_init()
>
> On Tue, Aug 30, 2011 at 01:29:49PM +0300, Dan Carpenter wrote:
> > > err3:
> > > free_irq(irq, hv_acpi_dev);
> > > err2:
> > > bus_unregister(&hv_bus);
> > > err1:
> > > hv_cleanup();
> >
> > Also here is an oldbie trick. You could use multiples of ten like
> > err30, err20, and err10. That way if you can add more error handling
> > in the middle without changing the numbering. I knew my GW-BASIC
> > experience would come in handy one day. :)
> >
> > The better way to label things is based on what happens when you get
> > there: err_irq, err_unregister, err_cleanup.
>
> Yes, that's the best way to do this, thanks for pointing it out.
I will fix this up.
Regards,
K. Y
>
> greg k-h
^ permalink raw reply
* RE: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: KY Srinivasan @ 2011-08-30 17:27 UTC (permalink / raw)
To: Greg KH
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
In-Reply-To: <20110829181502.GC19668@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Monday, August 29, 2011 2:15 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org
> Subject: Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
>
> On Sat, Aug 27, 2011 at 11:31:14AM -0700, K. Y. Srinivasan wrote:
> > Further cleanup of the hv drivers.
> >
> > 1) Cleanup reference counting.
> >
> > 2) Handle all block devices using the storvsc driver. I have modified
> > the implementation here based on Christoph's feedback on my earlier
> > implementation.
> >
> > 3) Fix bugs.
> >
> > 4) Accomodate some host side scsi emulation bugs.
> >
> > 5) In case of scsi errors off-line the device.
> >
> > This patch-set further reduces the size of Hyper-V drivers - the code is
> > about 10% smaller. This reduction is mainly because we have eliminated the
> > blkvsc driver.
>
> If my tracking is correct, I applied everything in this series except
> the following patches
> [PATCH 37/46] Staging: hv: vmbus: Check for events before messages
> [PATCH 41/46] Staging: hv: vmbus: Fix a bug in error handling in
> vmbus_bus_init()
> [PATCH 46/46] Staging: hv: Update the TODO file
>
> Please fix up patches 37 and 41 and resend, and for 46, that should be
> totally different as mentioned, but you might want to send a patch that
> at the least adds your name to the file at the bottom, as you wanted.
> Also note that the MAINTAINERS file should also be adjusted to match.
Thanks Greg. I will try to get these patches back to you as soon as possible.
Regards,
K. Y
^ permalink raw reply
* Re: [PATCH 37/46] Staging: hv: vmbus: Check for events before messages
From: Greg KH @ 2011-08-30 17:38 UTC (permalink / raw)
To: KY Srinivasan
Cc: devel@linuxdriverproject.org, Haiyang Zhang, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <6E21E5352C11B742B20C142EB499E048081B52F7@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Tue, Aug 30, 2011 at 05:06:39PM +0000, KY Srinivasan wrote:
> > On Sat, Aug 27, 2011 at 11:31:36AM -0700, K. Y. Srinivasan wrote:
> > > Conform to Windows specification by checking for events before messages.
> >
> > What specification?
> >
> > Care to provide a comment in the code that you are doing this in this
> > explicit order because of some rule that the hypervisor imposes on us?
>
> I am not sure if this is documented anywhere (publicly). In talking to Windows
> guys, they suggested this is the order in which it is done on Windows guests and suggested
> I should do the same. I will see if there is some public documentation that specifies this.
All you need to do is just document it in the code and I'll be happy.
We don't rely on external documentation for things to be changed, in
fact, there usually isn't any such thing :)
thanks,
greg k-h
^ permalink raw reply
* Re: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in connection.c
From: Greg KH @ 2011-08-30 17:41 UTC (permalink / raw)
To: KY Srinivasan
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <6E21E5352C11B742B20C142EB499E048081B5318@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Tue, Aug 30, 2011 at 05:11:57PM +0000, KY Srinivasan wrote:
> Thanks Greg. I will fix this. I got these patches out just before Hurricane Irene
> hit the east coast. While we were lucky that it was not as bad as was predicted,
> we lost power and we still don't have power. I have come to a public library in
> a nearby town to check my email. So, my responses will be sporadic over the
> next couple of days (until we get power). I will try to address the issues you
> have raised as quickly as possible.
Ouch, good luck with the power and other cleanup, hopefully you didn't
have any water damage.
I'm in no rush for further patches, that's being driven by your end :)
greg k-h
^ permalink raw reply
* Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: Greg KH @ 2011-08-30 17:43 UTC (permalink / raw)
To: KY Srinivasan
Cc: Olaf Hering, devel@linuxdriverproject.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <6E21E5352C11B742B20C142EB499E048081B5363@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Tue, Aug 30, 2011 at 05:22:54PM +0000, KY Srinivasan wrote:
>
>
> > -----Original Message-----
> > From: Olaf Hering [mailto:olaf@aepfle.de]
> > Sent: Tuesday, August 30, 2011 8:49 AM
> > To: KY Srinivasan
> > Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> > devel@linuxdriverproject.org; virtualization@lists.osdl.org
> > Subject: Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
> >
> > On Sat, Aug 27, K. Y. Srinivasan wrote:
> >
> > > 2) Handle all block devices using the storvsc driver. I have modified
> > > the implementation here based on Christoph's feedback on my earlier
> > > implementation.
> >
> > The upgrade path from hv_blkvsc to hv_storvsc is difficult.
> >
> > hv_storvsc does not provide the vmbus:hv_block modalias, so mkinitrd
> > does not know what module to choose when mkinitrd is called in a
> > previous kernel (like sles11sp1).
> >
> >
> > In a guest with both SCSI and IDE controllers the IDE disks are
> > discovered first, so the SCSI drives will also change their names.
> > Thats not a problem for data partitions because they could be mounted by
> > UUID or LABEL in fstab.
> > But its difficult to adjust /boot/grub/device.map for example because
> > the old IDE drives do not provide an identifier. What is the best way
> > to make sure the rename from hd* to sd* in such config files is done
> > correctly? Is it safe to assume that all drives with a class_id of
> > 32412632-86cb-44a2-9b5c50d1417354f5 are connected to IDE ports?
>
> The class_id is invariant as we are returning the guid of the device under class_id.
>
> So, if you see a IDE guid under class_id, you can be sure (a) it is an ide device and (b)
> it is a device managed via the PV drivers.
>
> >
> > localhost:~ # head /sys/bus/vmbus/devices/vmbus_0_{1,2,3,10,11}/class_id
> > ==> /sys/bus/vmbus/devices/vmbus_0_1/class_id <==
> > {32412632-86cb-44a2-9b5c50d1417354f5}
> >
> > ==> /sys/bus/vmbus/devices/vmbus_0_2/class_id <==
> > {32412632-86cb-44a2-9b5c50d1417354f5}
> >
> > ==> /sys/bus/vmbus/devices/vmbus_0_3/class_id <==
> > {32412632-86cb-44a2-9b5c50d1417354f5}
> >
> > ==> /sys/bus/vmbus/devices/vmbus_0_10/class_id <==
> > {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
> >
> > ==> /sys/bus/vmbus/devices/vmbus_0_11/class_id <==
> > {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
> >
> >
> > In my test system, the IDE drives are now discovered twice, once by
> > hv_storvsc and once by libata:
>
> This is a known (old problem). The way this was handled earlier was to have the
> modprobe rules in place to setup a dependency that would force the load of the
> hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
> driver succeeded, we would not load the native driver. In sles11 sp1, we had a rule for
> loading blkvsc. With the merge of blkvsc and storvsc, the only change we need to make
> is to have storvsc in the rule (instaed of blkvsc).
Why do we need a rule at all? Shouldn't the module dependancy stuff
handle the autoloading of the drivers properly from the initrd now that
the hotplug logic is hooked up properly?
What am I missing here?
Or is the hotplug code not working correctly?
greg k-h
^ permalink raw reply
* Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: Olaf Hering @ 2011-08-30 18:04 UTC (permalink / raw)
To: Greg KH
Cc: KY Srinivasan, devel@linuxdriverproject.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830174330.GE22868@kroah.com>
On Tue, Aug 30, Greg KH wrote:
> > > In my test system, the IDE drives are now discovered twice, once by
> > > hv_storvsc and once by libata:
> >
> > This is a known (old problem). The way this was handled earlier was to have the
> > modprobe rules in place to setup a dependency that would force the load of the
> > hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
> > driver succeeded, we would not load the native driver. In sles11 sp1, we had a rule for
> > loading blkvsc. With the merge of blkvsc and storvsc, the only change we need to make
> > is to have storvsc in the rule (instaed of blkvsc).
>
> Why do we need a rule at all? Shouldn't the module dependancy stuff
> handle the autoloading of the drivers properly from the initrd now that
> the hotplug logic is hooked up properly?
There is no plan to load hv_vmbus (or xen-platform-pci) earlier than
native drivers. That was the purpose of the modprobe.conf files. Now
that there is a vmbus, that fact could be checked before any other
attempt to load drivers is made and hv_vmbus should be loaded and all of
its devices have to be probed manually by modprobe `cat modulealias`.
> Or is the hotplug code not working correctly?
There is nothing to hotplug. hv_vmbus has to be loaded first so that it
can take over the devices. But it seems that there is no shutdown of the
emulated hardware, thats why the disk "sda" is shown twice.
I spot a flaw here.
KY, can hv_vmbus shutdown emulated hardware? At least the disks, because
cdroms are appearently still be handled by native drivers?
Olaf
^ permalink raw reply
* Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: Greg KH @ 2011-08-30 18:19 UTC (permalink / raw)
To: Olaf Hering
Cc: KY Srinivasan, devel@linuxdriverproject.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830180434.GA10090@aepfle.de>
On Tue, Aug 30, 2011 at 08:04:34PM +0200, Olaf Hering wrote:
> On Tue, Aug 30, Greg KH wrote:
>
> > > > In my test system, the IDE drives are now discovered twice, once by
> > > > hv_storvsc and once by libata:
> > >
> > > This is a known (old problem). The way this was handled earlier was to have the
> > > modprobe rules in place to setup a dependency that would force the load of the
> > > hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
> > > driver succeeded, we would not load the native driver. In sles11 sp1, we had a rule for
> > > loading blkvsc. With the merge of blkvsc and storvsc, the only change we need to make
> > > is to have storvsc in the rule (instaed of blkvsc).
> >
> > Why do we need a rule at all? Shouldn't the module dependancy stuff
> > handle the autoloading of the drivers properly from the initrd now that
> > the hotplug logic is hooked up properly?
>
> There is no plan to load hv_vmbus (or xen-platform-pci) earlier than
> native drivers.
Wait, what do you mean by "native drivers"?
Isn't the hv_vmbus drivers the "native drivers" happening here?
Or are you referring to the "emulated-slow-as-hell drivers" that are
used to boot the machine?
> That was the purpose of the modprobe.conf files. Now
> that there is a vmbus, that fact could be checked before any other
> attempt to load drivers is made and hv_vmbus should be loaded and all of
> its devices have to be probed manually by modprobe `cat modulealias`.
I agree with the first part, but no modprobe should ever need to be
done, the hotplug boot process should properly load those modules when
the vmbus devices are seen by the vmbus core and the hotplug events
generated, which in turn calls modprobe, right?
So there should not need to be any special module.conf file changes for
hv systems, with the exception that the "emulated" drivers should be
added to the blacklist.
> > Or is the hotplug code not working correctly?
>
> There is nothing to hotplug. hv_vmbus has to be loaded first so that it
> can take over the devices. But it seems that there is no shutdown of the
> emulated hardware, thats why the disk "sda" is shown twice.
>
> I spot a flaw here.
I agree :)
> KY, can hv_vmbus shutdown emulated hardware? At least the disks, because
> cdroms are appearently still be handled by native drivers?
They are? Ick, why can't the vmbus storage driver see a cdrom device?
It's just a scsi device, right?
thanks
greg k-h
^ permalink raw reply
* CFP: 4th Workshop on Many-Task Computing on Grids and Supercomputers (MTAGS) 2011 -- co-located with IEEE/ACM Supercomputing 2011
From: Ioan Raicu @ 2011-08-31 7:36 UTC (permalink / raw)
To: virtualization
[-- Attachment #1.1: Type: text/plain, Size: 9990 bytes --]
4th Workshop on Many-Task Computing on Grids and Supercomputers
(MTAGS) 2011
*http://datasys.cs.iit.edu/events/MTAGS11/index.html *
*Co-located with * *Supercomputing/SC 2011*
<http://sc11.supercomputing.org/> *
Seattle Washington -- November 14th, 2011*
News
* *Keynote Speaker: *Professor David Abramson from Monash University,
Australia
* *Special Issue on Data Intensive Computing in the Clouds in the
Springer Journal of Grid Computing*
<http://datasys.cs.iit.edu/events/JGC-DataCloud-2012/index.html>
* *The Second International Workshop on Data Intensive Computing in
the Clouds (DataCloud-SC11) 2011, co-located at Supercomputing/SC
2011, November 14th, 2011
<http://datasys.cs.iit.edu/events/DataCloud-SC11/index.html>*
Overview
The 4th workshop on Many-Task Computing on Grids and Supercomputers
(MTAGS) will provide the scientific community a dedicated forum for
presenting new research, development, and deployment efforts of
large-scale many-task computing (MTC) applications on large scale
clusters, Grids, Supercomputers, and Cloud Computing infrastructure.
MTC, the theme of the workshop encompasses loosely coupled applications,
which are generally composed of many tasks (both independent and
dependent tasks) to achieve some larger application goal. This workshop
will cover challenges that can hamper efficiency and utilization in
running applications on large-scale systems, such as local resource
manager scalability and granularity, efficient utilization of raw
hardware, parallel file system contention and scalability, data
management, I/O management, reliability at scale, and application
scalability. We welcome paper submissions on all topics related to MTC
on large scale systems. Papers will be peer-reviewed, and accepted
papers will be published in the workshop proceedings as part of the ACM
digital library (pending approval). The workshop will be co-located with
the IEEE/ACM Supercomputing 2011 Conference in Seattle Washington on
November 14th, 2011.
For more information, please see
http://datasys.cs.iit.edu/events/MTAGS11/
<http://datasys.cs.iit.edu/events/MTAGS11/index.html>. For more
information on past workshops, please see MTAGS10
<http://datasys.cs.iit.edu/events/MTAGS10/index.html>, MTAGS09
<http://datasys.cs.iit.edu/events/MTAGS09/index.html>, and MTAGS08
<http://datasys.cs.iit.edu/events/MTAGS08/index.html>. We also ran a
Special Issue on Many-Task Computing in the IEEE Transactions on
Parallel and Distributed Systems (TPDS)
<http://datasys.cs.iit.edu/events/TPDS_MTC/index.html> which has
appeared in June 2011; the proceedings can be found online at
http://www.computer.org/portal/web/csdl/abs/trans/td/2011/06/ttd201106toc.htm.
We, the workshop organizers, also published two papers that are highly
relevant to this workshop. One paper is titled "Toward Loosely Coupled
Programming on Petascale Systems
<http://www.cs.iit.edu/%7Eiraicu/research/publications/2008_SC08_Falkon_BGP.pdf>",
and was published in SC08 <http://sc08.supercomp.org/>; the second paper
is titled "Many-Task Computing for Grids and Supercomputers
<http://www.cs.iit.edu/%7Eiraicu/research/publications/2008_MTAGS08_MTC.pdf>",
which was published in MTAGS08
<http://datasys.cs.iit.edu/events/MTAGS08/index.html>.
Topics
We invite the submission of original work that is related to the topics
below. The papers can be either short (5 pages) position papers, or long
(10 pages) research papers. Topics of interest include (in the context
of Many-Task Computing):
* Compute Resource Management
o Scheduling
o Job execution frameworks
o Local resource manager extensions
o Performance evaluation of resource managers in use on large
scale systems
o Dynamic resource provisioning
o Techniques to manage many-core resources and/or GPUs
o Challenges and opportunities in running many-task workloads on
HPC systems
o Challenges and opportunities in running many-task workloads on
Cloud Computing infrastructure
* Storage architectures and implementations
o Distributed file systems
o Parallel file systems
o Distributed meta-data management
o Content distribution systems for large data
o Data caching frameworks and techniques
o Data management within and across data centers
o Data-aware scheduling
o Data-intensive computing applications
o Eventual-consistency storage usage and management
* Programming models and tools
o Map-reduce and its generalizations
o Many-task computing middleware and applications
o Parallel programming frameworks
o Ensemble MPI techniques and frameworks
o Service-oriented science applications
* Large-Scale Workflow Systems
o Workflow system performance and scalability analysis
o Scalability of workflow systems
o Workflow infrastructure and e-Science middleware
o Programming Paradigms and Models
* Large-Scale Many-Task Applications
o High-throughput computing (HTC) applications
o Data-intensive applications
o Quasi-supercomputing applications, deployments, and experiences
o Performance Evaluation
* Performance evaluation
o Real systems
o Simulations
o Reliability of large systems
Important Dates
* Abstract submission: September 2, 2011
* Paper submission: September 9, 2011
* Acceptance notification: October 7, 2011
* Final papers due: October 28, 2011
Paper Submission
Authors are invited to submit papers with unpublished, original work of
not more than 10 pages of double column text using single spaced 10
point size on 8.5 x 11 inch pages, as per ACM 8.5 x 11 manuscript
guidelines
(http://www.acm.org/publications/instructions_for_proceedings_volumes);
document templates can be found at
http://www.acm.org/sigs/publications/proceedings-templates. We are also
seeking position papers of no more than 5 pages in length. A 250 word
abstract (PDF format) must be submitted online at
https://cmt.research.microsoft.com/MTAGS2011/ before the deadline of
September 2nd, 2011 at 11:59PM PST; the final 5/10 page papers in PDF
format will be due on September 9th, 2011 at 11:59PM PST. Papers will be
peer-reviewed, and accepted papers will be published in the workshop
proceedings as part of the ACM digital library (pending approval).
Notifications of the paper decisions will be sent out by October 7th,
2011. Selected excellent work may be eligible for additional
post-conference publication as journal articles or book chapters, such
as the previous Special Issue on Many-Task Computing in the IEEE
Transactions on Parallel and Distributed Systems (TPDS)
<http://datasys.cs.iit.edu/events/TPDS_MTC/index.html> which has
appeared in June 2011. Submission implies the willingness of at least
one of the authors to register and present the paper. For more
information, please http://datasys.cs.iit.edu/events/MTAGS11/
<http://datasys.cs.iit.edu/events/MTAGS11/index.html>, or send email to
mtags11-chairs@datasys.cs.iit.edu
<mailto:mtags11-chairs@datasys.cs.iit.edu>.
Organization
<http://datasys.cs.iit.edu/events/MTAGS11/organization.html>
*General Chairs (mtags11-chairs@datasys.cs.iit.edu
<mailto:mtags11-chairs@datasys.cs.iit.edu>)*
* Ioan Raicu, Illinois Institute of Technology & Argonne National
Laboratory, USA
* Ian Foster, University of Chicago & Argonne National Laboratory, USA
* Yong Zhao, University of Electronic Science and Technology of China,
China
*Steering Committee*
* David Abramson, Monash University, Australia
* Jack Dongara, University of Tennessee, USA
* Geoffrey Fox, Indiana University, USA
* Manish Parashar, Rutgers University, USA
* Marc Snir, University of Illinois at Urbana Champaign, USA
* Xian-He Sun, Illinois Institute of Technology, USA
* Weimin Zheng, Tsinghua University, China
*Program Committee*
* Roger Barga, Microsoft Research, USA
* Mihai Budiu, Microsoft Research, USA
* Rajkumar Buyya, University of Melbourne, Australia
* Catalin Dumitrescu, Fermi National Labs, USA
* Alexandru Iosup, Delft University of Technology, Netherlands
* Florin Isaila, Universidad Carlos III de Madrid, Spain
* Kamil Iskra, Argonne National Laboratory, USA
* Hui Jin, Illinois Institute of Technology, USA
* Daniel S. Katz, University of Chicago, USA
* Tevfik Kosar, Louisiana State University, USA
* Zhiling Lan, Illinois Institute of Technology, USA
* Reagan Moore, University of North Carolina, Chappel Hill, USA
* Jose Moreira, IBM Research, USA
* Marlon Pierce, Indiana University, USA
* Judy Qiu, Indiana University, USA
* Lavanya Ramakrishnan, Lawrence Berkeley National Laboratory, USA
* Matei Ripeanu, University of British Columbia, Canada
* Alain Roy, University of Wisconsin, Madison, USA
* Edward Walker, Texas Advanced Computing Center, USA
* Mike Wilde, University of Chicago & Argonne National Laboratory, USA
* Matthew Woitaszek, The University Corporation for Atmospheric
Research, USA
* Ken Yocum, University of California at San Diego, USA
--
=================================================================
Ioan Raicu, Ph.D.
Assistant Professor, Illinois Institute of Technology (IIT)
Guest Research Faculty, Argonne National Laboratory (ANL)
=================================================================
Data-Intensive Distributed Systems Laboratory, CS/IIT
Distributed Systems Laboratory, MCS/ANL
=================================================================
Cel: 1-847-722-0876
Office: 1-312-567-5704
Email: iraicu@cs.iit.edu
Web: http://www.cs.iit.edu/~iraicu/
Web: http://datasys.cs.iit.edu/
=================================================================
=================================================================
[-- Attachment #1.2: Type: text/html, Size: 14736 bytes --]
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/virtualization
^ permalink raw reply
* CFP: The Second International Workshop on Data Intensive Computing in the Clouds (DataCloud-SC11) 2011 -- co-located with IEEE/ACM Supercomputing 2011
From: Ioan Raicu @ 2011-08-31 7:47 UTC (permalink / raw)
To: virtualization
[-- Attachment #1.1: Type: text/plain, Size: 7879 bytes --]
The Second International Workshop on Data Intensive Computing in the
Clouds (DataCloud-SC11) 2011
http://datasys.cs.iit.edu/events/DataCloud-SC11/
*Co-located with * *Supercomputing/SC 2011*
<http://sc11.supercomputing.org/> *
Seattle Washington -- November 14th, 2011*
News
* *Special Issue on Data Intensive Computing in the Clouds in the
Springer Journal of Grid Computing*
<http://datasys.cs.iit.edu/events/JGC-DataCloud-2012/index.html>
* *4th Workshop on Many-Task Computing on Grids and Supercomputers
(MTAGS) 2011, co-located at Supercomputing/SC 2011, November 14th,
2011 <http://datasys.cs.iit.edu/events/MTAGS11/index.html>*
Overview
Applications and experiments in all areas of science are becoming
increasingly complex and more demanding in terms of their computational
and data requirements. Some applications generate data volumes reaching
hundreds of terabytes and even petabytes. As scientific applications
become more data intensive, the management of data resources and
dataflow between the storage and compute resources is becoming the main
bottleneck. Analyzing, visualizing, and disseminating these large data
sets has become a major challenge and data intensive computing is now
considered as the "fourth paradigm" in scientific discovery after
theoretical, experimental, and computational science.
The second international workshop on Data-intensive Computing in the
Clouds (DataCloud-SC11) will provide the scientific community a
dedicated forum for discussing new research, development, and deployment
efforts in running data-intensive computing workloads on Cloud Computing
infrastructures. The DataCloud-SC11 workshop will focus on the use of
cloud-based technologies to meet the new data intensive scientific
challenges that are not well served by the current supercomputers, grids
or compute-intensive clouds. We believe the workshop will be an
excellent place to help the community define the current state,
determine future goals, and present architectures and services for
future clouds supporting data intensive computing.
For more information about the workshop, please see
http://datasys.cs.iit.edu/events/DataCloud-SC11/. To see the 1st
workshop's program agenda, and accepted papers and presentations, please
see http://www.cse.buffalo.edu/faculty/tkosar/datacloud2011/. We are
also running a Special Issue on Data Intensive Computing in the Clouds
<http://datasys.cs.iit.edu/events/JGC-DataCloud-2012/index.html> in the
Springer Journal of Grid Computing
<http://www.springer.com/computer/communication+networks/journal/10723>
with a paper submission deadline of August 16th 2011, which will appear
in print in June 2012.
Topics
* Data-intensive cloud computing applications, characteristics,
challenges
* Case studies of data intensive computing in the clouds
* Performance evaluation of data clouds, data grids, and data centers
* Energy-efficient data cloud design and management
* Data placement, scheduling, and interoperability in the clouds
* Accountability, QoS, and SLAs
* Data privacy and protection in a public cloud environment
* Distributed file systems for clouds
* Data streaming and parallelization
* New programming models for data-intensive cloud computing
* Scalability issues in clouds
* Social computing and massively social gaming
* 3D Internet and implications
* Future research challenges in data-intensive cloud computing
Important Dates
* Abstract submission: September 2, 2011
* Paper submission: September 9, 2011
* Acceptance notification: October 7, 2011
* Final papers due: October 28, 2011
Paper Submission
Authors are invited to submit papers with unpublished, original work of
not more than 10 pages of double column text using single spaced 10
point size on 8.5 x 11 inch pages, as per ACM 8.5 x 11 manuscript
guidelines
(http://www.acm.org/publications/instructions_for_proceedings_volumes);
document templates can be found at
http://www.acm.org/sigs/publications/proceedings-templates. We are also
seeking position papers of no more than 5 pages in length. A 250 word
abstract (PDF format) must be submitted online at
https://cmt.research.microsoft.com/DataCloud_SC11/ before the deadline
of September 2nd, 2011 at 11:59PM PST; the final 5/10 page papers in PDF
format will be due on September 9th, 2011 at 11:59PM PST. Papers will be
peer-reviewed, and accepted papers will be published in the workshop
proceedings as part of the ACM digital library (pending approval).
Notifications of the paper decisions will be sent out by October 7th,
2011. Selected excellent work may be eligible for additional
post-conference publication as journal articles. We are currently
running a Special Issue on Data Intensive Computing in the Clouds
<http://datasys.cs.iit.edu/events/JGC-DataCloud-2012/index.html> in the
Springer Journal of Grid Computing
<http://www.springer.com/computer/communication+networks/journal/10723>.
Submission implies the willingness of at least one of the authors to
register and present the paper. For more information, please see
http://datasys.cs.iit.edu/events/DataCloud-SC11/ or send email to
datacloud-sc11-chairs@datasys.cs.iit.edu
<mailto:datacloud-sc11-chairs@datasys.cs.iit.edu>.
Organization
<http://datasys.cs.iit.edu/events/DataCloud-SC11/organization.html>
*General Chairs (datacloud-sc11-chairs@datasys.cs.iit.edu
<mailto:datacloud-sc11-chairs@datasys.cs.iit.edu>)*
* Ioan Raicu, Illinois Institute of Technology & Argonne National
Laboratory, USA
* Tevfik Kosar, University at Buffalo, USA
* Roger Barga, Microsoft Research, USA
*Steering Committee*
* Ian Foster, University of Chicago & Argonne National Laboratory, USA
* Geoffrey Fox, Indiana University, USA
* James Hamilton, Amazon, USA
* Manish Parashar, Rutgers University, USA
* Dan Reed, Microsoft Research, USA
* Rich Wolski, University of California at Santa Barbara, USA
* Rong Chang, IBM, USA
*Program Committee*
* David Abramson, Monash University, Australia
* Abhishek Chandra, University of Minnesota, USA
* Yong Chen, Texas Tech University, USA
* Terence Critchlow, Pacific Northwest National Laboratory, USA
* Murat Demirbas, SUNY Buffalo, USA
* Jaliya Ekanayake, Microsoft Research, USA
* Rob Gillen, Oak Ridge National Laboratory, USA
* Maria Indrawan, Monash University, Australia
* Alexandru Iosup, Delft University of Technology, Netherlands
* Hui Jin, Illinois Institute of Technology, USA
* Dan S. Katz, University of Chicago, USA
* Gregor von Laszewski, Indiana University, USA
* Erwin Laure, CERN, Switzerland
* Reagan Moore, University of North Carolina at Chapel Hill, USA
* Jim Myers, Rensselaer Polytechnic Institute, USA
* Judy Qiu, Indiana University, USA
* Lavanya Ramakrishnan, Lawrence Berkeley National Laboratory, USA
* Florian Schintke, Zuse Institute Berlin, Germany
* Borja Sotomayor, University of Chicago, USA
* Ian Taylor, Cardiff University, UK
* Bernard Traversat, Oracle Corporation, USA
--
=================================================================
Ioan Raicu, Ph.D.
Assistant Professor, Illinois Institute of Technology (IIT)
Guest Research Faculty, Argonne National Laboratory (ANL)
=================================================================
Data-Intensive Distributed Systems Laboratory, CS/IIT
Distributed Systems Laboratory, MCS/ANL
=================================================================
Cel: 1-847-722-0876
Office: 1-312-567-5704
Email: iraicu@cs.iit.edu
Web: http://www.cs.iit.edu/~iraicu/
Web: http://datasys.cs.iit.edu/
=================================================================
=================================================================
[-- Attachment #1.2: Type: text/html, Size: 10784 bytes --]
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/virtualization
^ permalink raw reply
* CiteSearcher: a Google Scholar front-end for iOS and Android mobile devices
From: Ioan Raicu @ 2011-08-31 8:41 UTC (permalink / raw)
To: virtualization
[-- Attachment #1.1: Type: text/plain, Size: 2127 bytes --]
CiteSearcher v1.2search%20results.png
Google Scholar on your iPod, iPhone, iPad, and Android based mobile
devices
*http://datasys.cs.iit.edu/projects/CiteSearcher/*
CiteSearcher is a Google Scholar front-end for iOS and Android mobile
devices. With it, you can easily search Google Scholar for an author's
work, his/her Hirsch index (H-index,
http://en.wikipedia.org/wiki/H-index), and G-Index
(http://en.wikipedia.org/wiki/G-index).
For a detailed list of features and screenshots, see
http://datasys.cs.iit.edu/projects/CiteSearcher/details.html. For the
free downloads, see IOS
(http://itunes.apple.com/us/app/citesearcher/id453186643?mt=8) or
Android (https://market.android.com/details?id=datasys.iit). We plan to
maintain this software as long as there is demand from the community,
and improve it with new features and by supporting additional mobile
devices.
The lead developer of these applications is Kevin Brandstatter from the
DataSys Laboratory at Illinois Institute of Technology. If you would
like to signup to the CiteSearcher user mailing list in order to find
out information about future releases of CiteSearcher, please see
http://datasys.cs.iit.edu/mailman/listinfo/citesearcher-user. For any
comments or feedback, please write to
citesearcher-devel@datasys.cs.iit.edu. Bugs can be reported to
http://datasys.cs.iit.edu/projects/CiteSearcher/bugReport.php.
--
=================================================================
Ioan Raicu, Ph.D.
Assistant Professor, Illinois Institute of Technology (IIT)
Guest Research Faculty, Argonne National Laboratory (ANL)
=================================================================
Data-Intensive Distributed Systems Laboratory, CS/IIT
Distributed Systems Laboratory, MCS/ANL
=================================================================
Cel: 1-847-722-0876
Office: 1-312-567-5704
Email: iraicu@cs.iit.edu
Web: http://www.cs.iit.edu/~iraicu/
Web: http://datasys.cs.iit.edu/
=================================================================
=================================================================
[-- Attachment #1.2.1: Type: text/html, Size: 3701 bytes --]
[-- Attachment #1.2.2: search results.png --]
[-- Type: image/png, Size: 49607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/virtualization
^ permalink raw reply
* Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: Olaf Hering @ 2011-08-31 9:11 UTC (permalink / raw)
To: Greg KH
Cc: KY Srinivasan, devel@linuxdriverproject.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830181945.GC24865@kroah.com>
On Tue, Aug 30, Greg KH wrote:
> On Tue, Aug 30, 2011 at 08:04:34PM +0200, Olaf Hering wrote:
> > On Tue, Aug 30, Greg KH wrote:
> >
> > > > > In my test system, the IDE drives are now discovered twice, once by
> > > > > hv_storvsc and once by libata:
> > > >
> > > > This is a known (old problem). The way this was handled earlier was to have the
> > > > modprobe rules in place to setup a dependency that would force the load of the
> > > > hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
> > > > driver succeeded, we would not load the native driver. In sles11 sp1, we had a rule for
> > > > loading blkvsc. With the merge of blkvsc and storvsc, the only change we need to make
> > > > is to have storvsc in the rule (instaed of blkvsc).
> > >
> > > Why do we need a rule at all? Shouldn't the module dependancy stuff
> > > handle the autoloading of the drivers properly from the initrd now that
> > > the hotplug logic is hooked up properly?
> >
> > There is no plan to load hv_vmbus (or xen-platform-pci) earlier than
> > native drivers.
>
> Wait, what do you mean by "native drivers"?
native means drivers for emulated hardware: ata_piix, piix.
> Isn't the hv_vmbus drivers the "native drivers" happening here?
> Or are you referring to the "emulated-slow-as-hell drivers" that are
> used to boot the machine?
Not really. The virtual IDE controllers are emulated hardware, while the
virtual SCSI controllers are paravirtualized hardware. KY, correct my if
I'm wrong here.
> > That was the purpose of the modprobe.conf files. Now
> > that there is a vmbus, that fact could be checked before any other
> > attempt to load drivers is made and hv_vmbus should be loaded and all of
> > its devices have to be probed manually by modprobe `cat modulealias`.
>
> I agree with the first part, but no modprobe should ever need to be
> done, the hotplug boot process should properly load those modules when
> the vmbus devices are seen by the vmbus core and the hotplug events
> generated, which in turn calls modprobe, right?
With the IDE disks, the module loading order matters because both
ata_piix/piix and hv_storvsc will bind to them.
With the SCSI disks, only hv_storvsc will bind to them.
> So there should not need to be any special module.conf file changes for
> hv systems, with the exception that the "emulated" drivers should be
> added to the blacklist.
I agree, the modprobe.conf rules for hv should be removed. With this
patchset a rule to prevent ata_piix loading would hide all cdrom devices.
> > KY, can hv_vmbus shutdown emulated hardware? At least the disks, because
> > cdroms are appearently still be handled by native drivers?
>
> They are? Ick, why can't the vmbus storage driver see a cdrom device?
> It's just a scsi device, right?
The GUI does not seem to offer a way to attach an iso to a virtual SCSI
controller. It looks like one can add up to 4 SCSI controllers, each one
can have up to 64 disk images.
DVD devices can only be attached to the 2 virtual IDE controllers, one
can either attach iso images or physical hardware.
After some more testing it looks like the hv_blkvsc driver claimed the
ide major #3, so the ide_core could not bind to the emulated IDE
hardware. The modprobe.conf rules prevented that ata_piix gets loaded.
If I force a module load order of 'ata_piix ;hv_blkvsc' both ata_piix
and hv_blkvsc will bind to the same drive, just as shown in my previous
mail. So there is appearently no way to shutdown the IDE ports like it
is done with xen_emul_unplug= option for Xen guests.
Maybe some hack is needed for a hyper-v specific unplug if Windows does
indeed lack that feature. Now that ata_piix is compiled into the kernel,
there is nothing to a modprobe.conf rule can "fix".
Olaf
^ permalink raw reply
* RE: [PATCH 0000/0046] Staging: hv: Driver cleanup
From: KY Srinivasan @ 2011-08-31 14:18 UTC (permalink / raw)
To: Greg KH
Cc: Olaf Hering, devel@linuxdriverproject.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
In-Reply-To: <20110830174330.GE22868@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Tuesday, August 30, 2011 1:44 PM
> To: KY Srinivasan
> Cc: Olaf Hering; devel@linuxdriverproject.org; gregkh@suse.de; linux-
> kernel@vger.kernel.org; virtualization@lists.osdl.org
> Subject: Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
>
> On Tue, Aug 30, 2011 at 05:22:54PM +0000, KY Srinivasan wrote:
> >
> >
> > > -----Original Message-----
> > > From: Olaf Hering [mailto:olaf@aepfle.de]
> > > Sent: Tuesday, August 30, 2011 8:49 AM
> > > To: KY Srinivasan
> > > Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> > > devel@linuxdriverproject.org; virtualization@lists.osdl.org
> > > Subject: Re: [PATCH 0000/0046] Staging: hv: Driver cleanup
> > >
> > > On Sat, Aug 27, K. Y. Srinivasan wrote:
> > >
> > > > 2) Handle all block devices using the storvsc driver. I have modified
> > > > the implementation here based on Christoph's feedback on my earlier
> > > > implementation.
> > >
> > > The upgrade path from hv_blkvsc to hv_storvsc is difficult.
> > >
> > > hv_storvsc does not provide the vmbus:hv_block modalias, so mkinitrd
> > > does not know what module to choose when mkinitrd is called in a
> > > previous kernel (like sles11sp1).
> > >
> > >
> > > In a guest with both SCSI and IDE controllers the IDE disks are
> > > discovered first, so the SCSI drives will also change their names.
> > > Thats not a problem for data partitions because they could be mounted by
> > > UUID or LABEL in fstab.
> > > But its difficult to adjust /boot/grub/device.map for example because
> > > the old IDE drives do not provide an identifier. What is the best way
> > > to make sure the rename from hd* to sd* in such config files is done
> > > correctly? Is it safe to assume that all drives with a class_id of
> > > 32412632-86cb-44a2-9b5c50d1417354f5 are connected to IDE ports?
> >
> > The class_id is invariant as we are returning the guid of the device under
> class_id.
> >
> > So, if you see a IDE guid under class_id, you can be sure (a) it is an ide device
> and (b)
> > it is a device managed via the PV drivers.
> >
> > >
> > > localhost:~ # head /sys/bus/vmbus/devices/vmbus_0_{1,2,3,10,11}/class_id
> > > ==> /sys/bus/vmbus/devices/vmbus_0_1/class_id <==
> > > {32412632-86cb-44a2-9b5c50d1417354f5}
> > >
> > > ==> /sys/bus/vmbus/devices/vmbus_0_2/class_id <==
> > > {32412632-86cb-44a2-9b5c50d1417354f5}
> > >
> > > ==> /sys/bus/vmbus/devices/vmbus_0_3/class_id <==
> > > {32412632-86cb-44a2-9b5c50d1417354f5}
> > >
> > > ==> /sys/bus/vmbus/devices/vmbus_0_10/class_id <==
> > > {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
> > >
> > > ==> /sys/bus/vmbus/devices/vmbus_0_11/class_id <==
> > > {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
> > >
> > >
> > > In my test system, the IDE drives are now discovered twice, once by
> > > hv_storvsc and once by libata:
> >
> > This is a known (old problem). The way this was handled earlier was to have the
> > modprobe rules in place to setup a dependency that would force the load of
> the
> > hyper-v driver (blk / stor) ahead of the native driver and if the load of the PV
> > driver succeeded, we would not load the native driver. In sles11 sp1, we had a
> rule for
> > loading blkvsc. With the merge of blkvsc and storvsc, the only change we need
> to make
> > is to have storvsc in the rule (instaed of blkvsc).
>
> Why do we need a rule at all? Shouldn't the module dependancy stuff
> handle the autoloading of the drivers properly from the initrd now that
> the hotplug logic is hooked up properly?
>
> What am I missing here?
On sles11 the PV drivers are used to manage the root device. Autoloading is not
the issue here; to manage the root device, we want to load the Hyper-V disk driver
before the native Linux disk driver for the emulated IDE device.
>
> Or is the hotplug code not working correctly?
Hotplug code is working as expected; the issue is taking control of the root device and
preventing the same device being presented once through native drivers and once through
Hyper-V drivers.
Regards,
K. Y
>
> greg k-h
^ permalink raw reply
* RE: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in connection.c
From: KY Srinivasan @ 2011-08-31 14:21 UTC (permalink / raw)
To: Greg KH
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org,
Haiyang Zhang
In-Reply-To: <20110830174157.GD22868@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Tuesday, August 30, 2011 1:42 PM
> To: KY Srinivasan
> Cc: gregkh@suse.de; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; virtualization@lists.osdl.org; Haiyang Zhang
> Subject: Re: [PATCH 44/46] Staging: hv: vmbus: Fix checkpatch warnings in
> connection.c
>
> On Tue, Aug 30, 2011 at 05:11:57PM +0000, KY Srinivasan wrote:
> > Thanks Greg. I will fix this. I got these patches out just before Hurricane Irene
> > hit the east coast. While we were lucky that it was not as bad as was predicted,
> > we lost power and we still don't have power. I have come to a public library in
> > a nearby town to check my email. So, my responses will be sporadic over the
> > next couple of days (until we get power). I will try to address the issues you
> > have raised as quickly as possible.
>
> Ouch, good luck with the power and other cleanup, hopefully you didn't
> have any water damage.
>
> I'm in no rush for further patches, that's being driven by your end :)
Power was restored early this morning. Fortunately, except for lack power and
a few broken branches, we did not really feel the brunt of this hurricane. I am starting
work on addressing the issues you and others have raised.
Regards,
K. Y
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox