public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: adam radford <aradford@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, Bo.Yang@lsi.com
Subject: Re: [PATCH 7/11]: megaraid_sas: Add MegaRAID 9265/9285 specific functions: megaraid_sas_fusion.c
Date: Thu, 16 Dec 2010 14:57:36 +0100	[thread overview]
Message-ID: <4D0A1AD0.1040703@redhat.com> (raw)
In-Reply-To: <AANLkTik1KwdG+73gWCqGj7sROdxWfBYfKqH4t=rcQkhi@mail.gmail.com>

On 12/15/2010 04:04 AM, adam radford wrote:
> James/Linux-scsi,
>
> This patch adds the MegaRAID 9265/9285 specific functions contained in
> the file megaraid_sas_fusion.c.
>
> Signed-off-by: Adam Radford <aradford@gmail.com>
>
> Note: The patch has been included in-line below, and also as an
> attachment in case Gmail hoses the patch.
>   
> +/* Fusion OCR work queue */
> +void megasas_fusion_ocr_wq(struct work_struct *work)
> +{
> +	struct megasas_instance *instance =
> +		container_of(work, struct megasas_instance, work_init);
> +	struct scsi_cmnd scmd;
> +	struct scsi_device dev;
> +
> +	scmd.device = &dev;
> +	dev.host = instance->host;
> +	megasas_reset_fusion(&scmd);
> +}
>   
Hi Adam, Bo,

The function megasas_fusion_ocr_wq seems to be used already in patch 6/11 
and declared in 7/11 - this breaks bisectability.

Further my compiler complains about a large frame size.
Probably the 'struct scsi_device dev' is too large to be on stack.
make checkstack
...
0x000090f4 megasas_fusion_ocr_wq [megaraid_sas]:	1696

Tomas

> +
> +struct megasas_instance_template megasas_instance_template_fusion = {
> +	.fire_cmd = megasas_fire_cmd_fusion,
> +	.enable_intr = megasas_enable_intr_fusion,
> +	.disable_intr = megasas_disable_intr_fusion,
> +	.clear_intr = megasas_clear_intr_fusion,
> +	.read_fw_status_reg = megasas_read_fw_status_reg_fusion,
> +	.adp_reset = megasas_adp_reset_fusion,
> +	.check_reset = megasas_check_reset_fusion,
> +	.service_isr = megasas_isr_fusion,
> +	.tasklet = megasas_complete_cmd_dpc_fusion,
> +	.init_adapter = megasas_init_adapter_fusion,
> +	.build_and_issue_cmd = megasas_build_and_issue_cmd_fusion,
> +	.issue_dcmd = megasas_issue_dcmd_fusion,
> +};
>   


  reply	other threads:[~2010-12-16 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  3:04 [PATCH 7/11]: megaraid_sas: Add MegaRAID 9265/9285 specific functions: megaraid_sas_fusion.c adam radford
2010-12-16 13:57 ` Tomas Henzl [this message]
2010-12-16 16:58   ` adam radford
2010-12-16 17:13     ` adam radford
2010-12-17 10:42       ` Tomas Henzl
2010-12-17 13:13         ` James Bottomley
2010-12-17 17:30           ` adam radford
2010-12-17 17:46             ` adam radford
2010-12-21 20:28 ` Christoph Hellwig
2010-12-21 20:53   ` adam radford

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=4D0A1AD0.1040703@redhat.com \
    --to=thenzl@redhat.com \
    --cc=Bo.Yang@lsi.com \
    --cc=aradford@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    /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