All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kubascik <jeff.kubascik@dornerworks.com>
To: Julien Grall <julien@xen.org>, <xen-devel@lists.xenproject.org>
Cc: Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH v3 0/2] xen/arm: physical timer improvements
Date: Thu, 16 Jan 2020 16:52:42 -0500	[thread overview]
Message-ID: <4ea2a4ba-c952-826b-a5b5-4270ca121b48@dornerworks.com> (raw)
In-Reply-To: <443204d2-5766-6d36-3105-196528a4dd73@xen.org>

Hello Julien,

On 1/16/2020 4:25 PM, Julien Grall wrote:
> Hi Jeff,
> 
> Do you plan to resend the series? If not, I am happy to respin the
> series for you.

Feel free! Unfortunately, I currently don't have the bandwidth to keep this
patch moving along.

> Best regards,
> 
> On 11/12/2019 21:13, Jeff Kubascik wrote:
>> This patch set improves the emulation of the physical timer by removing the
>> physical timer offset and sign extend the TimerValue to better match the
>> behavior described in the ARMv8 Reference Manual (ARM DDI 0487E.a), section
>> D11.2.4.
>>
>> Changes in v2:
>> - Update commit message to specify reference manual version and section
>> - Change physical timer cval to hold hardware value
>> - Make sure to sign extend TimerValue on writes. This was done by first
>>    casting the r pointer to (int32_t *), dereferencing it, then casting
>>    to uint64_t. Please let me know if there is a more correct way to do
>>    this
>>
>> Changes in v3:
>> - Split TimerValue sign extension fix into separate patch
>> - Update commit message to mention physical timer cleanup
>> - Removed physical timer cval initialization line
>> - Changed TimerValue sign extension to (uint64_t)(int32_t)*r
>> - Account for condition where cval < boot_count
>>
>> Jeff Kubascik (2):
>>    xen/arm: remove physical timer offset
>>    xen/arm: sign extend writes to TimerValue
>>
>>   xen/arch/arm/vtimer.c        | 34 ++++++++++++++++++----------------
>>   xen/include/asm-arm/domain.h |  3 ---
>>   2 files changed, 18 insertions(+), 19 deletions(-)
>>
> 
> --
> Julien Grall
> 

Sincerely,
Jeff Kubascik

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2020-01-16 21:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 21:13 [Xen-devel] [PATCH v3 0/2] xen/arm: physical timer improvements Jeff Kubascik
2019-12-11 21:13 ` [Xen-devel] [PATCH v3 1/2] xen/arm: remove physical timer offset Jeff Kubascik
2019-12-18 14:20   ` Julien Grall
2020-01-17 21:24     ` Jeff Kubascik
2020-01-23 12:28       ` Julien Grall
2019-12-11 21:13 ` [Xen-devel] [PATCH v3 2/2] xen/arm: sign extend writes to TimerValue Jeff Kubascik
2019-12-18 14:24   ` Julien Grall
2020-01-17 21:29     ` Jeff Kubascik
2020-01-18 11:49       ` Julien Grall
2020-01-21 14:43         ` Jeff Kubascik
2020-01-16 21:25 ` [Xen-devel] [PATCH v3 0/2] xen/arm: physical timer improvements Julien Grall
2020-01-16 21:52   ` Jeff Kubascik [this message]

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=4ea2a4ba-c952-826b-a5b5-4270ca121b48@dornerworks.com \
    --to=jeff.kubascik@dornerworks.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.