On Thu, 26 Jul 2012 17:35:13 +0800
Xiao Guangrong wrote:
> > Is this patch really safe for all architectures?
> >
> > IS_ERR_VALUE() casts -MAX_ERRNO to unsigned long and then does comparison.
> > Isn't it possible to conflict with valid pfns?
> >
>
> See IS_ERR_VALUE():
>
> #define IS_ERR_VA
On 07/26/2012 05:20 PM, Takuya Yoshikawa wrote:
> On Thu, 26 Jul 2012 11:56:15 +0300
> Avi Kivity wrote:
>
>> Since my comments are better done as a separate patch, I applied all
>> three patches. Thanks!
>
> Is this patch really safe for all architectures?
>
> IS_ERR_VALUE() casts -MAX_ERRNO
On 07/26/2012 04:56 PM, Avi Kivity wrote:
> On 07/26/2012 06:58 AM, Xiao Guangrong wrote:
>> Currently, kvm allocates some pages and use them as error indicators,
>> it wastes memory and is not good for scalability
>>
>> Base on Avi's suggestion, we use the error codes instead of these pages
>> to
On Thu, 26 Jul 2012 11:56:15 +0300
Avi Kivity wrote:
> Since my comments are better done as a separate patch, I applied all
> three patches. Thanks!
Is this patch really safe for all architectures?
IS_ERR_VALUE() casts -MAX_ERRNO to unsigned long and then does comparison.
Isn't it possible to
On 07/26/2012 06:58 AM, Xiao Guangrong wrote:
> Currently, kvm allocates some pages and use them as error indicators,
> it wastes memory and is not good for scalability
>
> Base on Avi's suggestion, we use the error codes instead of these pages
> to indicate the error conditions
>
>
> +static pf
5 matches
Mail list logo