RISC-V: Modularize common match conditions for trigger
v4 cover RISC-V: Modularize common match conditions for trigger
According to RISC-V Debug specification ratified version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), the enabled privilege levels of the trigger is common match conditions for all the types of the trigger.
This series modularize the code for checking the privilege levels of type 2/3/6 triggers by implementing functions trigger_common_match() and trigger_priv_match().
Additional match conditions, such as CSR tcontrol and textra, can be further implemented into trigger_common_match() in the future.
[1]: https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vote
[2]: https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asciidoc
Changes from v3:
- Change this series to target Debug Spec. version 0.13
Changes from v2:
- Explicitly mention the targeting version of RISC-V Debug Spec.
Changes from v1:
- Fix typo
- Add commit description for changing behavior of looping the triggers when we check type 2 triggers.
Alvin Chang (4):
target/riscv: Add functions for common matching conditions of trigger target/riscv: Apply modularized matching conditions for breakpoint target/riscv: Apply modularized matching conditions for watchpoint target/riscv: Apply modularized matching conditions for icount trigger
target/riscv/debug.c | 124 +++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 41 deletions(-)
Signature · 1 line
2.34.1
PATCH v4 1/4 target/riscv: Add functions for common matching conditions of trigger
According to RISC-V Debug specification version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), there are several common matching conditions before firing a trigger, including the enabled privilege levels of the trigger.
This commit adds trigger_common_match() to prepare the common matching conditions for the type 2/3/6 triggers. For now, we just implement trigger_priv_match() to check if the enabled privilege levels of the trigger match CPU's current privilege level.
[1]: https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vote
[2]: https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asciidoc
--- target/riscv/debug.c | 70 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+)
target/riscv/debug.c +70 -0
@@ -241,6 +241,76 @@ static void do_trigger_action(CPURISCVState *env, target_ulong trigger_index) } } +/* +* Check the privilege level of specific trigger matches CPU's current privilege +* level. +*/ +static bool trigger_priv_match (CPURISCVState *env,trigger_type_t type, +int trigger_index) +{ +target_ulong ctrl = env->tdata1[trigger_index]; + +switch (type) { +case TRIGGER_TYPE_AD_MATCH : +/* type 2 trigger cannot be fired in VU/VS mode */ +if (env->virt_enabled) { +return false; + } +/* check U/S/M bit against current privilege level */ +if ((ctrl >>3 ) &BIT (env->priv)) { +return true; + } +break ; +case TRIGGER_TYPE_AD_MATCH6 : +if (env->virt_enabled) { +/* check VU/VS bit against current privilege level */ +if ((ctrl >>23 ) &BIT (env->priv)) { +return true; + } + }else { +/* check U/S/M bit against current privilege level */ +if ((ctrl >>3 ) &BIT (env->priv)) { +return true; + } + } +break ; +case TRIGGER_TYPE_INST_CNT : +if (env->virt_enabled) { +/* check VU/VS bit against current privilege level */ +if ((ctrl >>25 ) &BIT (env->priv)) { +return true; + } + }else { +/* check U/S/M bit against current privilege level */ +if ((ctrl >>6 ) &BIT (env->priv)) { +return true; + } + } +break ; +case TRIGGER_TYPE_INT : +case TRIGGER_TYPE_EXCP : +case TRIGGER_TYPE_EXT_SRC : +qemu_log_mask (LOG_UNIMP ,"trigger type: %d is not supported\n" , type); +break ; +case TRIGGER_TYPE_NO_EXIST : +case TRIGGER_TYPE_UNAVAIL : +qemu_log_mask (LOG_GUEST_ERROR ,"trigger type: %d does not exist\n" , + type); +break ; +default : +g_assert_not_reached (); + } + +return false; +} + +/* Common matching conditions for all types of the triggers. */ +static bool trigger_common_match (CPURISCVState *env,trigger_type_t type, +int trigger_index) +{ +return trigger_priv_match (env, type, trigger_index); +} +/* type 2 trigger */ static uint32_t type2_breakpoint_size (CPURISCVState *env,target_ulong ctrl)
Signature · 1 line
2.34.1
Re: [PATCH v4 1/4] target/riscv: Add functions for common matching conditions of trigger
Quoted 11 lines · Alvin Chang via
According to RISC-V Debug specification version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), there are several common matching conditions before firing a trigger, including the enabled privilege levels of the trigger.
This commit adds
trigger_common_match()to prepare the common matching conditions for the type 2/3/6 triggers. For now, we just implementtrigger_priv_match()to check if the enabled privilege levels of the trigger match CPU's current privilege level.
Quoted 4 lines
[1]: https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vote
[2]: https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asciidocSigned-off-by Alvin Chang <[email protected]>
Alistair
Quoted 89 lines
--- target/riscv/debug.c | 70 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+)target/riscv/debug.c +70
-1@@ -241,6 +241,76 @@ static void do_trigger_action(CPURISCVState *env, target_ulong trigger_index) } } +/* +* Check the privilege level of specific trigger matches CPU's current privilege +* level. +*/ +static bool trigger_priv_match (CPURISCVState *env,trigger_type_t type, +int trigger_index) +{ +target_ulong ctrl = env->tdata1[trigger_index]; + +switch (type) { +case TRIGGER_TYPE_AD_MATCH : +/* type 2 trigger cannot be fired in VU/VS mode */ +if (env->virt_enabled) { +return false; + } +/* check U/S/M bit against current privilege level */ +if ((ctrl >>3 ) &BIT (env->priv)) { +return true; + } +break ; +case TRIGGER_TYPE_AD_MATCH6 : +if (env->virt_enabled) { +/* check VU/VS bit against current privilege level */ +if ((ctrl >>23 ) &BIT (env->priv)) { +return true; + } + }else { +/* check U/S/M bit against current privilege level */ +if ((ctrl >>3 ) &BIT (env->priv)) { +return true; + } + } +break ; +case TRIGGER_TYPE_INST_CNT : +if (env->virt_enabled) { +/* check VU/VS bit against current privilege level */ +if ((ctrl >>25 ) &BIT (env->priv)) { +return true; + } + }else { +/* check U/S/M bit against current privilege level */ +if ((ctrl >>6 ) &BIT (env->priv)) { +return true; + } + } +break ; +case TRIGGER_TYPE_INT : +case TRIGGER_TYPE_EXCP : +case TRIGGER_TYPE_EXT_SRC : +qemu_log_mask (LOG_UNIMP ,"trigger type: %d is not supported\n" , type); +break ; +case TRIGGER_TYPE_NO_EXIST : +case TRIGGER_TYPE_UNAVAIL : +qemu_log_mask (LOG_GUEST_ERROR ,"trigger type: %d does not exist\n" , + type); +break ; +default : +g_assert_not_reached (); + } + +return false; +} + +/* Common matching conditions for all types of the triggers. */ +static bool trigger_common_match (CPURISCVState *env,trigger_type_t type, +int trigger_index) +{ +return trigger_priv_match (env, type, trigger_index); +} +/* type 2 trigger */ static uint32_t type2_breakpoint_size (CPURISCVState *env,target_ulong ctrl) --2.34.1
PATCH v4 2/4 target/riscv: Apply modularized matching conditions for breakpoint
In reply to Alvin Chang viaWe have implemented trigger_common_match(), which checks if the enabled privilege levels of the trigger match CPU's current privilege level. Remove the related code in riscv_cpu_debug_check_breakpoint() and invoke trigger_common_match() to check the privilege levels of the type 2 and type 6 triggers for the breakpoints.
This commit also changes the behavior of looping the triggers. In previous implementation, if we have a type 2 trigger and env->virt_enabled is true, we directly return false to stop the loop. Now we keep looping all the triggers until we find a matched trigger.
Only the execution bit and the executed PC should be futher checked in riscv_cpu_debug_check_breakpoint().
--- target/riscv/debug.c | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-)
target/riscv/debug.c +6 -20
@@ -855,21 +855,17 @@ bool riscv_cpu_debug_check_breakpoint(CPUState *cs)for (i =0 ; i <RV_MAX_TRIGGERS ; i++) { trigger_type =get_trigger_type (env, i); +if (!trigger_common_match (env, trigger_type, i)) { +continue ; + } +switch (trigger_type) {case TRIGGER_TYPE_AD_MATCH : -/* type 2 trigger cannot be fired in VU/VS mode */ -if (env->virt_enabled) { -return false; - } - ctrl = env->tdata1[i]; pc = env->tdata2[i];if ((ctrl &TYPE2_EXEC ) && (bp->pc == pc)) { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } +return true; }break ;case TRIGGER_TYPE_AD_MATCH6 :
@@ -877,17 +873,7 @@ bool riscv_cpu_debug_check_breakpoint(CPUState *cs) pc = env->tdata2[i];if ((ctrl &TYPE6_EXEC ) && (bp->pc == pc)) { -if (env->virt_enabled) { -/* check VU/VS bit against current privilege level */ -if ((ctrl >>23 ) &BIT (env->priv)) { -return true; - } - }else { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } - } +return true; }break ;default :
Signature · 1 line
2.34.1
PATCH v4 3/4 target/riscv: Apply modularized matching conditions for watchpoint
In reply to Alvin Chang viaWe have implemented trigger_common_match(), which checks if the enabled privilege levels of the trigger match CPU's current privilege level. Remove the related code in riscv_cpu_debug_check_watchpoint() and invoke trigger_common_match() to check the privilege levels of the type 2 and type 6 triggers for the watchpoints.
This commit also changes the behavior of looping the triggers. In previous implementation, if we have a type 2 trigger and env->virt_enabled is true, we directly return false to stop the loop. Now we keep looping all the triggers until we find a matched trigger.
Only load/store bits and loaded/stored address should be further checked in riscv_cpu_debug_check_watchpoint().
--- target/riscv/debug.c | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-)
target/riscv/debug.c +6 -20
@@ -899,13 +899,12 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp)for (i =0 ; i <RV_MAX_TRIGGERS ; i++) { trigger_type =get_trigger_type (env, i); +if (!trigger_common_match (env, trigger_type, i)) { +continue ; + } +switch (trigger_type) {case TRIGGER_TYPE_AD_MATCH : -/* type 2 trigger cannot be fired in VU/VS mode */ -if (env->virt_enabled) { -return false; - } - ctrl = env->tdata1[i]; addr = env->tdata2[i]; flags =0 ;
@@ -918,10 +917,7 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp) }if ((wp->flags & flags) && (wp->vaddr == addr)) { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } +return true; }break ;case TRIGGER_TYPE_AD_MATCH6 :
@@ -937,17 +933,7 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp) }if ((wp->flags & flags) && (wp->vaddr == addr)) { -if (env->virt_enabled) { -/* check VU/VS bit against current privilege level */ -if ((ctrl >>23 ) &BIT (env->priv)) { -return true; - } - }else { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } - } +return true; }break ;default :
Signature · 1 line
2.34.1
Re: [PATCH v4 3/4] target/riscv: Apply modularized matching conditions for watchpoint
Quoted 12 lines · Alvin Chang via
We have implemented
trigger_common_match(), which checks if the enabled privilege levels of the trigger match CPU's current privilege level. Remove the related code inriscv_cpu_debug_check_watchpoint()and invoketrigger_common_match()to check the privilege levels of the type 2 and type 6 triggers for the watchpoints.This commit also changes the behavior of looping the triggers. In previous implementation, if we have a type 2 trigger and
env->virt_enabledis true, we directly return false to stop the loop. Now we keep looping all the triggers until we find a matched trigger.
Quoted 4 lines
Only load/store bits and loaded/stored address should be further checked in
riscv_cpu_debug_check_watchpoint().Signed-off-by Alvin Chang <[email protected]>
Alistair
Quoted 61 lines
--- target/riscv/debug.c | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-)target/riscv/debug.c +6
-21@@ -899,13 +899,12 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp)for (i =0 ; i <RV_MAX_TRIGGERS ; i++) { trigger_type =get_trigger_type (env, i); +if (!trigger_common_match (env, trigger_type, i)) { +continue ; + } +switch (trigger_type) {case TRIGGER_TYPE_AD_MATCH : -/* type 2 trigger cannot be fired in VU/VS mode */ -if (env->virt_enabled) { -return false; - } - ctrl = env->tdata1[i]; addr = env->tdata2[i]; flags =0 ;@@ -918,10 +917,7 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp) }if ((wp->flags & flags) && (wp->vaddr == addr)) { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } +return true; }break ;case TRIGGER_TYPE_AD_MATCH6 :@@ -937,17 +933,7 @@ bool riscv_cpu_debug_check_watchpoint(CPUState *cs, CPUWatchpoint *wp) }if ((wp->flags & flags) && (wp->vaddr == addr)) { -if (env->virt_enabled) { -/* check VU/VS bit against current privilege level */ -if ((ctrl >>23 ) &BIT (env->priv)) { -return true; - } - }else { -/* check U/S/M bit against current privilege level */ -if ((ctrl >>3 ) &BIT (env->priv)) { -return true; - } - } +return true; }break ;default : --2.34.1
PATCH v4 4/4 target/riscv: Apply modularized matching conditions for icount trigger
In reply to Alvin Chang viaWe have implemented trigger_common_match(), which checks if the enabled privilege levels of the trigger match CPU's current privilege level. We can invoke trigger_common_match() to check the privilege levels of the type 3 triggers.
--- target/riscv/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
target/riscv/debug.c +1 -1
@@ -624,7 +624,7 @@ void helper_itrigger_match(CPURISCVState *env)if (get_trigger_type (env, i) !=TRIGGER_TYPE_INST_CNT ) {continue ; } -if (check_itrigger_priv (env, i)) { +if (!trigger_common_match (env,TRIGGER_TYPE_INST_CNT , i)) {continue ; } count =itrigger_get_count (env, i);
Signature · 1 line
2.34.1
Re: [PATCH v4 4/4] target/riscv: Apply modularized matching conditions for icount trigger
Quoted 7 lines · Alvin Chang via
We have implemented
trigger_common_match(), which checks if the enabled privilege levels of the trigger match CPU's current privilege level. We can invoketrigger_common_match()to check the privilege levels of the type 3 triggers.Signed-off-by Alvin Chang <[email protected]>
Alistair
Quoted 21 lines
--- target/riscv/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)target/riscv/debug.c +1
-2@@ -624,7 +624,7 @@ void helper_itrigger_match(CPURISCVState *env)if (get_trigger_type (env, i) !=TRIGGER_TYPE_INST_CNT ) {continue ; } -if (check_itrigger_priv (env, i)) { +if (!trigger_common_match (env,TRIGGER_TYPE_INST_CNT , i)) {continue ; } count =itrigger_get_count (env, i); --2.34.1
Hi Alistair,
Please also take a look at this series, I guess it is ready to be applied, thanks!
BRs,
Alvin
Quoted 42 lines
-----Original Message-----
From: Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Sent: Tuesday, February 27, 2024 9:24 AM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Subject: [PATCH v4 0/4] RISC-V: Modularize common match conditions for triggerAccording to RISC-V Debug specification ratified version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), the enabled privilege levels of the trigger is common match conditions for all the types of the trigger.
This series modularize the code for checking the privilege levels of type 2/3/6 triggers by implementing functions
trigger_common_match()andtrigger_priv_match().Additional match conditions, such as CSR tcontrol and textra, can be further implemented into
trigger_common_match()in the future.[1]: https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vote
[2]: https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asciidocChanges from v3:
- Change this series to target Debug Spec. version 0.13Changes from v2:
- Explicitly mention the targeting version of RISC-V Debug Spec.Changes from v1:
- Fix typo
- Add commit description for changing behavior of looping the triggers when we check type 2 triggers.Alvin Chang (4):
target/riscv: Add functions for common matching conditions of trigger target/riscv: Apply modularized matching conditions for breakpoint target/riscv: Apply modularized matching conditions for watchpoint target/riscv: Apply modularized matching conditions for icount trigger
Quoted 5 lines
target/riscv/debug.c | 124 +++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 41 deletions(-)--
2.34.1
CONFIDENTIALITY NOTICE:
This e-mail (and its attachments) may contain confidential and legally privileged information or information protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein is strictly prohibited. In this case, please immediately notify the sender by return e-mail, delete the message (and any accompanying documents) and destroy all printed hard copies. Thank you for your cooperation.
Copyright ANDES TECHNOLOGY CORPORATION - All Rights Reserved.
Quoted 4 lines · Alvin Che-Chia Chang(張哲嘉)
Hi Alistair,
Please also take a look at this series, I guess it is ready to be applied, thanks!
This is all acked now, do you mind rebasing on
https://github.com/alistair23/qemu/tree/riscv-to-apply.next and sending a new version
Alistair
Quoted 58 lines
BRs,
AlvinQuoted 42 lines
-----Original Message-----
From: Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Sent: Tuesday, February 27, 2024 9:24 AM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Subject: [PATCH v4 0/4] RISC-V: Modularize common match conditions for triggerAccording to RISC-V Debug specification ratified version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), the enabled privilege levels of the trigger is common match conditions for all the types of the trigger.
This series modularize the code for checking the privilege levels of type 2/3/6 triggers by implementing functions
trigger_common_match()andtrigger_priv_match().Additional match conditions, such as CSR tcontrol and textra, can be further implemented into
trigger_common_match()in the future.[1]: https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vote
[2]: https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asciidocChanges from v3:
- Change this series to target Debug Spec. version 0.13Changes from v2:
- Explicitly mention the targeting version of RISC-V Debug Spec.Changes from v1:
- Fix typo
- Add commit description for changing behavior of looping the triggers when we check type 2 triggers.Alvin Chang (4):
target/riscv: Add functions for common matching conditions of trigger target/riscv: Apply modularized matching conditions for breakpoint target/riscv: Apply modularized matching conditions for watchpoint target/riscv: Apply modularized matching conditions for icount triggerQuoted 5 lines
target/riscv/debug.c | 124 +++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 41 deletions(-)--
2.34.1CONFIDENTIALITY NOTICE:
This e-mail (and its attachments) may contain confidential and legally privileged information or information protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein is strictly prohibited. In this case, please immediately notify the sender by return e-mail, delete the message (and any accompanying documents) and destroy all printed hard copies. Thank you for your cooperation.
Copyright ANDES TECHNOLOGY CORPORATION - All Rights Reserved.
Quoted 15 lines
-----Original Message-----
From: Alistair Francis <[email protected]>
Sent: Tuesday, June 4, 2024 9:58 AM
To: Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [PATCH v4 0/4] RISC-V: Modularize common match conditions for trigger[EXTERNAL MAIL]
Quoted 1 line · Alvin Che-Chia Chang(張哲嘉)
Quoted 7 lines
Quoted 3 lines
Hi Alistair,
Please also take a look at this series, I guess it is ready to be applied, thanks!
This is all acked now, do you mind rebasing on
https://github.com/alistair23/qemu/tree/riscv-to-apply.next and sending a new version
Done, please check patch v5.
I also took care of Daniel's latest patch:
https://github.com/alistair23/qemu/commit/0099f6053410f5611796213b723e908cfc8055eb
BRs,
Alvin
Quoted 65 lines
Alistair
Quoted 19 lines
BRs,
AlvinQuoted 14 lines
-----Original Message-----
From: Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Sent: Tuesday, February 27, 2024 9:24 AM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Alvin Che-Chia Chang(張哲嘉) <[email protected]>
Subject: [PATCH v4 0/4] RISC-V: Modularize common match conditions for triggerAccording to RISC-V Debug specification ratified version 0.13 [1] (also applied to version 1.0 [2] but it has not been ratified yet), the enabled privilege levels of the trigger is common match conditions for
all the types of the trigger.
Quoted 42 lines
Quoted 33 lines
This series modularize the code for checking the privilege levels of type 2/3/6 triggers by implementing functions
trigger_common_match()andtrigger_priv_match().Additional match conditions, such as CSR tcontrol and textra, can be further implemented into
trigger_common_match()in the future.[1]:
https://github.com/riscv/riscv-debug-spec/releases/tag/task_group_vo
te
[2]:
https://github.com/riscv/riscv-debug-spec/releases/tag/1.0.0-rc1-asc
iidocChanges from v3:
- Change this series to target Debug Spec. version 0.13Changes from v2:
- Explicitly mention the targeting version of RISC-V Debug Spec.Changes from v1:
- Fix typo
- Add commit description for changing behavior of looping the triggers when we check type 2 triggers.Alvin Chang (4):
target/riscv: Add functions for common matching conditions of trigger target/riscv: Apply modularized matching conditions for breakpoint target/riscv: Apply modularized matching conditions for watchpoint target/riscv: Apply modularized matching conditions for icount
triggerQuoted 6 lines
target/riscv/debug.c | 124 +++++++++++++++++++++++++++++-------------- 1 file changed, 83 insertions(+), 41 deletions(-)--
2.34.1CONFIDENTIALITY NOTICE:
Quoted 9 lines
Quoted 1 line
This e-mail (and its attachments) may contain confidential and legally
privileged information or information protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein is strictly prohibited. In this case, please immediately notify the sender by return e-mail, delete the message (and any accompanying documents) and destroy all printed hard copies. Thank you for your cooperation.
Quoted 2 lines
Copyright ANDES TECHNOLOGY CORPORATION - All Rights Reserved.
CONFIDENTIALITY NOTICE:
This e-mail (and its attachments) may contain confidential and legally privileged information or information protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein is strictly prohibited. In this case, please immediately notify the sender by return e-mail, delete the message (and any accompanying documents) and destroy all printed hard copies. Thank you for your cooperation.
Copyright ANDES TECHNOLOGY CORPORATION - All Rights Reserved.