All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"agraf@suse.de" <agraf@suse.de>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug registers
Date: Mon, 23 Jul 2012 16:02:05 +0000	[thread overview]
Message-ID: <500D757D.3030305@freescale.com> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D03DD59C8@039-SN2MPN1-023.039d.mgd.msft.net>

On 07/23/2012 10:48 AM, Bhushan Bharat-R65777 wrote:
> 
> 
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 9:12 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-ppc@vger.kernel.org; agraf@suse.de; kvm@vger.kernel.org; Bhushan Bharat-
>> R65777
>> Subject: Re: [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug
>> registers
>>
>> This will exceed the array size if userspace asks to access IAC3/4 on an e500-
>> family chip.
> 
> No , is not the array size already set to maximum. But yes we should not let IAC3/4 being accessed for e500 (FSL_BOOKE).
> 
>>
>> Why not just set the array at the max size unconditionally?
> 
> This is already coded this way. Please see the struct is this patch.

Sorry, I misread the array declaration.

-Scott



WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"agraf@suse.de" <agraf@suse.de>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug registers
Date: Mon, 23 Jul 2012 11:02:05 -0500	[thread overview]
Message-ID: <500D757D.3030305@freescale.com> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D03DD59C8@039-SN2MPN1-023.039d.mgd.msft.net>

On 07/23/2012 10:48 AM, Bhushan Bharat-R65777 wrote:
> 
> 
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Monday, July 23, 2012 9:12 PM
>> To: Bhushan Bharat-R65777
>> Cc: kvm-ppc@vger.kernel.org; agraf@suse.de; kvm@vger.kernel.org; Bhushan Bharat-
>> R65777
>> Subject: Re: [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug
>> registers
>>
>> This will exceed the array size if userspace asks to access IAC3/4 on an e500-
>> family chip.
> 
> No , is not the array size already set to maximum. But yes we should not let IAC3/4 being accessed for e500 (FSL_BOOKE).
> 
>>
>> Why not just set the array at the max size unconditionally?
> 
> This is already coded this way. Please see the struct is this patch.

Sorry, I misread the array declaration.

-Scott

  reply	other threads:[~2012-07-23 16:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 11:19 [PATCH v2] booke: Added ONE_REG interface for IAC/DAC debug registers Bharat Bhushan
2012-07-23 11:31 ` Bharat Bhushan
2012-07-23 15:42 ` Scott Wood
2012-07-23 15:42   ` Scott Wood
2012-07-23 15:48   ` Bhushan Bharat-R65777
2012-07-23 15:48     ` Bhushan Bharat-R65777
2012-07-23 16:02     ` Scott Wood [this message]
2012-07-23 16:02       ` Scott Wood
2012-07-23 17:41     ` Alexander Graf
2012-07-23 17:41       ` Alexander Graf
2012-07-24  1:04       ` Bhushan Bharat-R65777
2012-07-24  1:04         ` Bhushan Bharat-R65777
2012-07-24 12:46         ` Alexander Graf
2012-07-24 12:46           ` Alexander Graf
2012-07-24 13:26           ` Bhushan Bharat-R65777
2012-07-24 13:26             ` Bhushan Bharat-R65777
2012-07-24 14:56             ` Alexander Graf
2012-07-24 14:56               ` Alexander Graf

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=500D757D.3030305@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B07421@freescale.com \
    --cc=R65777@freescale.com \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.