From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] powerpc/kvm: Handle the boundary condition correctly
Date: Mon, 26 Aug 2013 12:26:01 +0000 [thread overview]
Message-ID: <87k3j8ejjq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <932EC6E7-BC15-474F-9E8B-4321B2126BE4@suse.de>
Alexander Graf <agraf@suse.de> writes:
> On 26.08.2013, at 05:28, Aneesh Kumar K.V wrote:
>
>> Alexander Graf <agraf@suse.de> writes:
>>
>>> On 23.08.2013, at 04:31, Aneesh Kumar K.V wrote:
>>>
>>>> Alexander Graf <agraf@suse.de> writes:
>>>>
>>>>> On 22.08.2013, at 12:37, Aneesh Kumar K.V wrote:
>>>>>
>>>>>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>>>>>
>>>>> Isn't this you?
>>>>
>>>> Yes. The patches are generated using git format-patch and sent by
>>>> git send-email. That's how it always created patches for me. I am not sure if
>>>> there is a config I can change to avoid having From:
>>>>
>>>>>
>>>>>>
>>>>>> We should be able to copy upto count bytes
>>>>>
>>>>> Why?
>>>>>
>>>>
>>>> Without this we end up doing
>>>>
>>>> + struct kvm_get_htab_buf {
>>>> + struct kvm_get_htab_header header;
>>>> + /*
>>>> + * Older kernel required one extra byte.
>>>> + */
>>>> + unsigned long hpte[3];
>>>> + } hpte_buf;
>>>>
>>>>
>>>> even though we are only looking for one hpte entry.
>>>
>>> Ok, please give me an example with real numbers and why it breaks.
>>>
>>>>
>>>> http://mid.gmane.org/1376995766-16526-4-git-send-email-aneesh.kumar@linux.vnet.ibm.com
>>>>
>>
>> Didn't quiet get what you are looking for. As explained before, we now
>> need to pass an array with array size 3 even though we know we need to
>> read only 2 entries because kernel doesn't loop correctly.
>
> But we need to do that regardless, because newer QEMU needs to be able to run on older kernels, no?
>
yes. So use space will have to pass an array of size 3. But that should
not prevent us from fixing this right ?
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] powerpc/kvm: Handle the boundary condition correctly
Date: Mon, 26 Aug 2013 17:44:01 +0530 [thread overview]
Message-ID: <87k3j8ejjq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <932EC6E7-BC15-474F-9E8B-4321B2126BE4@suse.de>
Alexander Graf <agraf@suse.de> writes:
> On 26.08.2013, at 05:28, Aneesh Kumar K.V wrote:
>
>> Alexander Graf <agraf@suse.de> writes:
>>
>>> On 23.08.2013, at 04:31, Aneesh Kumar K.V wrote:
>>>
>>>> Alexander Graf <agraf@suse.de> writes:
>>>>
>>>>> On 22.08.2013, at 12:37, Aneesh Kumar K.V wrote:
>>>>>
>>>>>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>>>>>
>>>>> Isn't this you?
>>>>
>>>> Yes. The patches are generated using git format-patch and sent by
>>>> git send-email. That's how it always created patches for me. I am not sure if
>>>> there is a config I can change to avoid having From:
>>>>
>>>>>
>>>>>>
>>>>>> We should be able to copy upto count bytes
>>>>>
>>>>> Why?
>>>>>
>>>>
>>>> Without this we end up doing
>>>>
>>>> + struct kvm_get_htab_buf {
>>>> + struct kvm_get_htab_header header;
>>>> + /*
>>>> + * Older kernel required one extra byte.
>>>> + */
>>>> + unsigned long hpte[3];
>>>> + } hpte_buf;
>>>>
>>>>
>>>> even though we are only looking for one hpte entry.
>>>
>>> Ok, please give me an example with real numbers and why it breaks.
>>>
>>>>
>>>> http://mid.gmane.org/1376995766-16526-4-git-send-email-aneesh.kumar@linux.vnet.ibm.com
>>>>
>>
>> Didn't quiet get what you are looking for. As explained before, we now
>> need to pass an array with array size 3 even though we know we need to
>> read only 2 entries because kernel doesn't loop correctly.
>
> But we need to do that regardless, because newer QEMU needs to be able to run on older kernels, no?
>
yes. So use space will have to pass an array of size 3. But that should
not prevent us from fixing this right ?
-aneesh
next prev parent reply other threads:[~2013-08-26 12:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 11:37 [PATCH] powerpc/kvm: Handle the boundary condition correctly Aneesh Kumar K.V
2013-08-22 11:49 ` Aneesh Kumar K.V
2013-08-22 16:48 ` Alexander Graf
2013-08-22 16:48 ` Alexander Graf
2013-08-23 3:31 ` Aneesh Kumar K.V
2013-08-23 3:43 ` Aneesh Kumar K.V
2013-08-23 4:28 ` Benjamin Herrenschmidt
2013-08-23 4:28 ` Benjamin Herrenschmidt
2013-08-25 18:09 ` Alexander Graf
2013-08-25 18:09 ` Alexander Graf
2013-08-25 18:16 ` Alexander Graf
2013-08-25 18:16 ` Alexander Graf
2013-08-26 3:28 ` Aneesh Kumar K.V
2013-08-26 3:40 ` Aneesh Kumar K.V
2013-08-26 11:10 ` Alexander Graf
2013-08-26 11:10 ` Alexander Graf
2013-08-26 12:14 ` Aneesh Kumar K.V [this message]
2013-08-26 12:26 ` Aneesh Kumar K.V
2013-09-25 15:42 ` Aneesh Kumar K.V
2013-09-25 15:54 ` Aneesh Kumar K.V
2013-09-25 15:51 ` Alexander Graf
2013-09-25 15:51 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2013-08-11 18:20 Aneesh Kumar K.V
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=87k3j8ejjq.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.